Triple
T24638054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMD 645-series diesel engine |
E609867
|
entity |
| Predicate | usedInLocomotiveSeries |
P156871
|
FINISHED |
| Object | EMD SD40 |
—
|
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 SD40 | Statement: [EMD 645-series diesel engine, usedInLocomotiveSeries, EMD SD40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLocomotiveSeries Context triple: [EMD 645-series diesel engine, usedInLocomotiveSeries, EMD SD40]
-
A.
usedLocomotives
Indicates that an entity employed locomotives as tools, resources, or means to perform an action or fulfill a function.
-
B.
laterLocomotiveType
Indicates that one locomotive type succeeds or comes after another in time, representing a later development or version in locomotive design.
-
C.
hasLocomotive
Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
-
D.
typeOfLocomotivesProduced
Indicates the specific kinds or categories of locomotives that are manufactured or produced by an entity.
-
E.
locomotiveWorks
Indicates a relationship where an entity is a facility or company that builds, repairs, or maintains locomotives.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:33 a.m.