Triple
T6759391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Pacific Railway |
E154551
|
entity |
| Predicate | laterUsedMotivePower |
P14429
|
FINISHED |
| Object | diesel locomotives |
—
|
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 locomotives | Statement: [Northern Pacific Railway, laterUsedMotivePower, diesel locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUsedMotivePower Context triple: [Northern Pacific Railway, laterUsedMotivePower, diesel locomotives]
-
A.
hasMotivePowerType
chosen
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
B.
laterPropulsion
Indicates that one propulsion system, method, or event occurs after another in time.
-
C.
motive
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
D.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
E.
transferredPowerTo
Indicates that one entity has passed control, authority, or energy to another entity.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.