Triple
T6592484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 171 |
E148394
|
entity |
| Predicate | hasCabEnds |
P65309
|
FINISHED |
| Object | gangwayed cab ends on some units |
—
|
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: gangwayed cab ends on some units | Statement: [British Rail Class 171, hasCabEnds, gangwayed cab ends on some units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabEnds Context triple: [British Rail Class 171, hasCabEnds, gangwayed cab ends on some units]
-
A.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
B.
hasCabType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
C.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
D.
cableEnd
Indicates that one entity represents an endpoint or terminal position of a cable in relation to another entity.
-
E.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.