Triple
T25077753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf, Mobile and Ohio Railroad |
E628097
|
entity |
| Predicate | usedMotivePowerFromManufacturer |
P138023
|
FINISHED |
| Object | EMD |
—
|
NE NERFINISHED |
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: EMD | Statement: [Gulf, Mobile and Ohio Railroad, usedMotivePowerFromManufacturer, EMD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMotivePowerFromManufacturer Context triple: [Gulf, Mobile and Ohio Railroad, usedMotivePowerFromManufacturer, EMD]
-
A.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
B.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
-
D.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
E.
usedManufacturer
chosen
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:21 a.m.