Triple
T31027708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRH380B |
E790626
|
entity |
| Predicate | trainControlSystem |
P115681
|
FINISHED |
| Object | CTCS |
—
|
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: CTCS | Statement: [CRH380B, trainControlSystem, CTCS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainControlSystem Context triple: [CRH380B, trainControlSystem, CTCS]
-
A.
trainControl
Indicates that one entity exercises authority over or manages the operation, direction, or behavior of another entity in a training or instructional context.
-
B.
controlsSystem
chosen
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
C.
trainOperation
Indicates that an entity is engaged in operating, running, or managing the movement and service of a train.
-
D.
railwayControlledBy
Indicates that the operation, management, or authority over a railway is exercised by a specified controlling entity.
-
E.
controlProtocol
Indicates that one entity governs, regulates, or coordinates the behavior or operations of another according to a defined set of rules or procedures.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 8:58 p.m.