Triple
T25779970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pacific AC-9 |
E649259
|
entity |
| Predicate | whyNotCabForward |
P159255
|
FINISHED |
| Object | coal-fired |
—
|
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: coal-fired | Statement: [Southern Pacific AC-9, whyNotCabForward, coal-fired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whyNotCabForward Context triple: [Southern Pacific AC-9, whyNotCabForward, coal-fired]
-
A.
hasCabPosition
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
-
B.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
C.
crewCab
Indicates that a vehicle has a crew cab configuration, meaning its cabin is designed to seat multiple occupants in both front and rear rows.
-
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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe5f81388190a7352c5782b19d80 |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 5:37 a.m.