Triple
T13455501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND/BMT Division |
E311220
|
entity |
| Predicate | hasTrainWidth |
P81651
|
FINISHED |
| Object | wider than IRT Division trains |
—
|
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: wider than IRT Division trains | Statement: [IND/BMT Division, hasTrainWidth, wider than IRT Division trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainWidth Context triple: [IND/BMT Division, hasTrainWidth, wider than IRT Division trains]
-
A.
hasRailWidth
chosen
Indicates that one entity has a specified width measurement for its rail or rails.
-
B.
hasTailTrain
Indicates that one entity possesses or is characterized by a tail-like train extending from it.
-
C.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
D.
trackWidth
Indicates the lateral distance between two parallel tracks or wheels, typically measured from center to center.
-
E.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaefc52448190b30d7999f44a9765 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.