Triple
T20658988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMD SD40-2 |
E507704
|
entity |
| Predicate | notableRebuildProgram |
P26232
|
FINISHED |
| Object | SD40-3 rebuilds |
—
|
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: SD40-3 rebuilds | Statement: [EMD SD40-2, notableRebuildProgram, SD40-3 rebuilds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRebuildProgram Context triple: [EMD SD40-2, notableRebuildProgram, SD40-3 rebuilds]
-
A.
reconstructionProgram
chosen
Indicates a program or initiative designed to rebuild, restore, or structurally improve something that has been damaged, degraded, or is otherwise in need of renewal.
-
B.
notableNationalProgram
Indicates that an entity is recognized as a significant or prominent program at the national level.
-
C.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
D.
notableGlobalProgram
Indicates that an entity is recognized as a significant, widely acknowledged program with impact or prominence at a global scale.
-
E.
notablePlan
Indicates that an entity is recognized for having a significant or noteworthy plan associated with it.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.