Triple
T29890432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 717 |
E759134
|
entity |
| Predicate | hasCabEndFeature |
P194751
|
FINISHED |
| Object | emergency end doors |
—
|
LITERAL FINISHED |
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: emergency end doors | Statement: [British Rail Class 717, hasCabEndFeature, emergency end doors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabEndFeature Context triple: [British Rail Class 717, hasCabEndFeature, emergency end doors]
-
A.
hasCabAtEachEnd
Indicates that something (typically a vehicle or train) has a cab located at both of its ends.
-
B.
hasCabPosition
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
-
C.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
D.
hasGangwayAtCabEnd
Indicates that a vehicle or unit has a gangway located at its cab end, allowing passage between connected units from that end.
-
E.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
- F. None of above. chosen
Provenance (4 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: April 29, 2026, 6:02 p.m.