metaeval/reqeval-ambiguity-detection · Datasets at Hugging Face

Unnamed: 0 int64 1 139	ID stringlengths 7 12	Sentence stringlengths 63 557	Detected as stringclasses 2 values
101	railway#50	Throughout the duration of the shunting group call, <referential>it</referential> shall be possible for any member of the shunting group to speak to all other members of the group, using the PTT function (as described in sections 5.2.2.53, 6.2.2.12 and 7.2.2.20), except during transmission of the link assurance signal.	NOCUOUS
102	railway#51	The shunting leader can then choose the moment when <referential>he</referential> takes or rejects the call.	INNOCUOUS
103	railway#52	In this case, the safety device will alert the driver only if the link assurance signal has failed or if <referential>it</referential> is cancelled.	INNOCUOUS
104	railway#53	The 300ms represents <referential>our</referential> current best estimate of the QoS figure, although this will need to be confirmed through user trials.	NOCUOUS
105	railway#54	Each authority can decide whether <referential>it</referential> wishes to use synchronised BTSs.	INNOCUOUS
106	railway#55	The network shall terminate the ongoing VGCS/VBS call if <referential>it</referential> receives the 3-digit sequence “***” transmitted via DTMF signals.	NOCUOUS
107	railway#56	The network shall send the SET-PARAMETER message with the attribute “D-ATT = T”1 [EN 301 515, Index [6]] to the mobile station of the talking subscriber if <referential>it</referential> receives the 3- digit sequence “###” transmitted via DTMF or the group call SETUP message2 from a controller terminal.	NOCUOUS
108	railway#57-1	When the network has detected the 3-digit DTMF sequence “###” transmitted via DTMF from a controller terminal and if the controller was not previously talking <referential>it</referential> should indicate its recognition by playing a single DTMF grant tone “#” of duration of 100ms  5ms to be sent to that controller terminal only.	NOCUOUS
109	railway#57-2	When the network has detected the 3-digit DTMF sequence “###” transmitted via DTMF from a controller terminal and if the controller was not previously talking it should indicate <referential>its</referential> recognition by playing a single DTMF grant tone “#” of duration of 100ms  5ms to be sent to that controller terminal only.	NOCUOUS
110	railway#58	The network shall send the SET-PARAMETER message with the attribute “D-ATT = F”3 [EN 301 515, Index [6]] to the mobile of the talking subscriber only if <referential>it</referential> has received the 3-digit sequence “#**” transmitted via DTMF from all the talking controllers4.	NOCUOUS
111	railway#59	Many of the railway specific standards referenced are Pre-standards (eg [prEN 50155, ENV 50121, prEN 50125]) and should be re-examined for <referential>their</referential> applicability to the EIRENE system if any modifications are made to these standards in the future.	INNOCUOUS
112	railway#60	Each of the other cabs on the train will be contacted using <referential>its</referential> functional number (registered by the other drivers prior to the establishment of the call).	NOCUOUS
113	railway#61	Upon registration, the mobile shall be accessible by calling the MSISDN or the Engine or Coach number with which <referential>it</referential> is associated.	INNOCUOUS
114	railway#62	The Cab radio system shall provide a means for the driver to terminate established calls which <referential>he</referential> is authorised to terminate.	INNOCUOUS
115	home#01	The DigitalHome programmable Appliance Manager shall provide for management of a home’s small appliances, including lighting units, by allowing a user to turn <referential>them</referential> on or off as desired.	NOCUOUS
116	home#02	Although the product produced under this document will be a “prototype” version, all modules and components of this prototype version shall be designed and implemented in such a manner that <referential>it</referential> may be incorporated in a fully specified commercial version of the DigitalHome System.	NOCUOUS
117	home#03	The DigitalHome System shall provide users with online documentation about the DigitalHome system installed in <referential>their</referential> home.	INNOCUOUS
118	space#01	The FCP shall, if the NEFU ICP fails to send <referential>its</referential> ICP Ready signal, mask out that ICP, but continue to use the NE.16.	INNOCUOUS
119	space#02	Each rate group has some number of tasks associated with <referential>it</referential>, and <referential>it</referential> also has a rate for those tasks.	INNOCUOUS
120	space#03	The enabled tasks are then unblocked at the rate given in <referential>its</referential> associated rate group.	NOCUOUS
121	space#04-1	An API call is available for the task to call to block <referential>itself</referential> when it is finished with its cyclic processing.	NOCUOUS
122	space#04-2	An API call is available for the task to call to block itself when <referential>it</referential> is finished with its cyclic processing.	NOCUOUS
123	space#04-3	An API call is available for the task to call to block itself when it is finished with <referential>its</referential> cyclic processing.	NOCUOUS
124	space#05	There is up to a full major frame from notification of an impending mode change to acting on <referential>it</referential> in minor frame 0 of the next major frame plus the time <referential>it</referential> takes during the next minor frame 0 to switch tasking.	NOCUOUS
125	space#06	The scheduler shall execute cyclic tasks, providing an API call to allow the application to block until <referential>its</referential> next iteration.	NOCUOUS
126	space#07	The scheduler shall give tasks priority values according to <referential>their</referential> rate - the higher the rate, the higher the priority.	NOCUOUS
127	space#08	The scheduler shall provide a mechanism to inform a task when <referential>it</referential> did not complete during the previous frame and restart <referential>it</referential> at the beginning of the task.	NOCUOUS
128	space#09	All tasks in rate groups and <referential>their</referential> corresponding schedules for all vehicle modes will be setup at system initialization.	NOCUOUS
129	space#10	Tasks in a rate group must suspend on a scheduler API call at the top of <referential>their</referential> execution loop.	INNOCUOUS
130	space#11	For hardware exceptions and reserved exceptions, the FTSS shall make the error type and <referential>its</referential> context data available to the application, then return from the exception handler to the task that was running when the exception occurred.	NOCUOUS
131	space#12	Messages are addressed with a global unique communication identifier that routes <referential>them</referential> to the appropriate virtual group (VG) and socket.	INNOCUOUS
132	space#13	This restriction does NOT apply to the ICPs since <referential>they</referential> are running as simplex VGs.	INNOCUOUS
133	space#14	The FTSS shall mask out a babbling NE or ICP within 40 milliseconds after <referential>it</referential> is detected.	NOCUOUS
134	space#15	Synchronous message passing sockets shall queue outgoing messages until <referential>they</referential> are transmitted at frame boundaries.	NOCUOUS
135	space#16	"Pipes may be opened by multiple receiving tasks if <referential>they</referential> are created with the broadcast"" capability; otherwise <referential>they</referential> may only be opened by one receiving task."""	NOCUOUS
136	space#17	"Communication services shall provide the capability to create pipe""s which ""broadcast"" <referential>their</referential> messages to all virtual groups."""	NOCUOUS
137	space#18	If the broadcast option is used, each virtual group should open the pipe and read from <referential>it</referential> to avoid flow control problems.	NOCUOUS
138	space#19	The application software shall have the capability to reset a permanently failed channel to <referential>its</referential> initial recovery state.	NOCUOUS
139	space#20	Redundancy Management picks up where <referential>it</referential> left off in these attempts.	INNOCUOUS

101

railway#50

Throughout the duration of the shunting group call, <referential>it</referential> shall be possible for any member of the shunting group to speak to all other members of the group, using the PTT function (as described in sections 5.2.2.53, 6.2.2.12 and 7.2.2.20), except during transmission of the link assurance signal.

NOCUOUS

102

railway#51

The shunting leader can then choose the moment when <referential>he</referential> takes or rejects the call.

INNOCUOUS

103

railway#52

In this case, the safety device will alert the driver only if the link assurance signal has failed or if <referential>it</referential> is cancelled.

INNOCUOUS

104

railway#53

The 300ms represents <referential>our</referential> current best estimate of the QoS figure, although this will need to be confirmed through user trials.

NOCUOUS

105

railway#54

Each authority can decide whether <referential>it</referential> wishes to use synchronised BTSs.

INNOCUOUS

106

railway#55

The network shall terminate the ongoing VGCS/VBS call if <referential>it</referential> receives the 3-digit sequence “***” transmitted via DTMF signals.

NOCUOUS

107

railway#56

The network shall send the SET-PARAMETER message with the attribute “D-ATT = T”1 [EN 301 515, Index [6]] to the mobile station of the talking subscriber if <referential>it</referential> receives the 3- digit sequence “###” transmitted via DTMF or the group call SETUP message2 from a controller terminal.

NOCUOUS

108

railway#57-1

When the network has detected the 3-digit DTMF sequence “###” transmitted via DTMF from a controller terminal and if the controller was not previously talking <referential>it</referential> should indicate its recognition by playing a single DTMF grant tone “#” of duration of 100ms  5ms to be sent to that controller terminal only.

NOCUOUS

109

railway#57-2

When the network has detected the 3-digit DTMF sequence “###” transmitted via DTMF from a controller terminal and if the controller was not previously talking it should indicate <referential>its</referential> recognition by playing a single DTMF grant tone “#” of duration of 100ms  5ms to be sent to that controller terminal only.

NOCUOUS

110

railway#58

The network shall send the SET-PARAMETER message with the attribute “D-ATT = F”3 [EN 301 515, Index [6]] to the mobile of the talking subscriber only if <referential>it</referential> has received the 3-digit sequence “#**” transmitted via DTMF from all the talking controllers4.

NOCUOUS

111

railway#59

Many of the railway specific standards referenced are Pre-standards (eg [prEN 50155, ENV 50121, prEN 50125]) and should be re-examined for <referential>their</referential> applicability to the EIRENE system if any modifications are made to these standards in the future.

INNOCUOUS

112

railway#60

Each of the other cabs on the train will be contacted using <referential>its</referential> functional number (registered by the other drivers prior to the establishment of the call).

NOCUOUS

113

railway#61

Upon registration, the mobile shall be accessible by calling the MSISDN or the Engine or Coach number with which <referential>it</referential> is associated.

INNOCUOUS

114

railway#62

The Cab radio system shall provide a means for the driver to terminate established calls which <referential>he</referential> is authorised to terminate.

INNOCUOUS

115

home#01

The DigitalHome programmable Appliance Manager shall provide for management of a home’s small appliances, including lighting units, by allowing a user to turn <referential>them</referential> on or off as desired.

NOCUOUS

116

home#02

Although the product produced under this document will be a “prototype” version, all modules and components of this prototype version shall be designed and implemented in such a manner that <referential>it</referential> may be incorporated in a fully specified commercial version of the DigitalHome System.

NOCUOUS

117

home#03

The DigitalHome System shall provide users with online documentation about the DigitalHome system installed in <referential>their</referential> home.

INNOCUOUS

118

space#01

The FCP shall, if the NEFU ICP fails to send <referential>its</referential> ICP Ready signal, mask out that ICP, but continue to use the NE.16.

INNOCUOUS

119

space#02

Each rate group has some number of tasks associated with <referential>it</referential>, and <referential>it</referential> also has a rate for those tasks.

INNOCUOUS

120

space#03

The enabled tasks are then unblocked at the rate given in <referential>its</referential> associated rate group.

NOCUOUS

121

space#04-1

An API call is available for the task to call to block <referential>itself</referential> when it is finished with its cyclic processing.

NOCUOUS

122

space#04-2

An API call is available for the task to call to block itself when <referential>it</referential> is finished with its cyclic processing.

NOCUOUS

123

space#04-3

An API call is available for the task to call to block itself when it is finished with <referential>its</referential> cyclic processing.

NOCUOUS

124

space#05

There is up to a full major frame from notification of an impending mode change to acting on <referential>it</referential> in minor frame 0 of the next major frame plus the time <referential>it</referential> takes during the next minor frame 0 to switch tasking.

NOCUOUS

125

space#06

The scheduler shall execute cyclic tasks, providing an API call to allow the application to block until <referential>its</referential> next iteration.

NOCUOUS

126

space#07

The scheduler shall give tasks priority values according to <referential>their</referential> rate - the higher the rate, the higher the priority.

NOCUOUS

127

space#08

The scheduler shall provide a mechanism to inform a task when <referential>it</referential> did not complete during the previous frame and restart <referential>it</referential> at the beginning of the task.

NOCUOUS

128

space#09

All tasks in rate groups and <referential>their</referential> corresponding schedules for all vehicle modes will be setup at system initialization.

NOCUOUS

129

space#10

Tasks in a rate group must suspend on a scheduler API call at the top of <referential>their</referential> execution loop.

INNOCUOUS

130

space#11

For hardware exceptions and reserved exceptions, the FTSS shall make the error type and <referential>its</referential> context data available to the application, then return from the exception handler to the task that was running when the exception occurred.

NOCUOUS

131

space#12

Messages are addressed with a global unique communication identifier that routes <referential>them</referential> to the appropriate virtual group (VG) and socket.

INNOCUOUS

132

space#13

This restriction does NOT apply to the ICPs since <referential>they</referential> are running as simplex VGs.

INNOCUOUS

133

space#14

The FTSS shall mask out a babbling NE or ICP within 40 milliseconds after <referential>it</referential> is detected.

NOCUOUS

134

space#15

Synchronous message passing sockets shall queue outgoing messages until <referential>they</referential> are transmitted at frame boundaries.

NOCUOUS

135

space#16

"Pipes may be opened by multiple receiving tasks if <referential>they</referential> are created with the broadcast"" capability; otherwise <referential>they</referential> may only be opened by one receiving task."""

NOCUOUS

136

space#17

"Communication services shall provide the capability to create pipe""s which ""broadcast"" <referential>their</referential> messages to all virtual groups."""

NOCUOUS

137

space#18

If the broadcast option is used, each virtual group should open the pipe and read from <referential>it</referential> to avoid flow control problems.

NOCUOUS

138

space#19

The application software shall have the capability to reset a permanently failed channel to <referential>its</referential> initial recovery state.

NOCUOUS

139

space#20

Redundancy Management picks up where <referential>it</referential> left off in these attempts.

INNOCUOUS