Triple
T36221866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R211 series |
E1047867
|
entity |
| Predicate | designedForSignalingSystem |
P187809
|
FINISHED |
| Object | CBTC |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: CBTC | Statement: [R211 series, designedForSignalingSystem, CBTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForSignalingSystem Context triple: [R211 series, designedForSignalingSystem, CBTC]
-
A.
isUsedInSignallingSystems
chosen
Indicates that something functions as a component or mechanism within a system designed to transmit, convey, or process signals.
-
B.
signallingSystem
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
-
C.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
D.
usesRailwaySignallingSystem
Indicates that one entity operates or applies a particular railway signalling system in the context of train or rail traffic control.
-
E.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:09 p.m.