Triple
T31593852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midland Railway – Butterley |
E806169
|
entity |
| Predicate | secondaryTractionType |
P196504
|
FINISHED |
| Object | diesel |
—
|
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: diesel | Statement: [Midland Railway – Butterley, secondaryTractionType, diesel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTractionType Context triple: [Midland Railway – Butterley, secondaryTractionType, diesel]
-
A.
secondaryTraction
Indicates a supporting or additional influence, pull, or driving force that complements a primary source of traction or momentum in a relationship or process.
-
B.
typicalTractionType
Indicates the usual or most common type of traction mechanism associated with an entity (such as how it is typically powered or driven).
-
C.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
-
D.
secondaryTraffic
Indicates that there is an additional, indirect, or subordinate flow of traffic associated with a primary traffic stream or event.
-
E.
successorTractionType
Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: April 30, 2026, 10:29 p.m.