Triple
T22730717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atchison, Topeka and Santa Fe Railway |
E562125
|
entity |
| Predicate | beganDieselization |
P127242
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Atchison, Topeka and Santa Fe Railway, beganDieselization, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganDieselization Context triple: [Atchison, Topeka and Santa Fe Railway, beganDieselization, 1930s]
-
A.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
B.
beganCommercialProduction
Indicates that an entity started producing something commercially, marking the commencement of its large-scale or market-oriented production.
-
C.
modernizationStartDate
chosen
Indicates the date on which a modernization process or upgrade for the entity was initiated.
-
D.
enteredDieselLocomotiveMarketInDecade
Indicates that an entity began participating in or selling products in the diesel locomotive market during the specified decade.
-
E.
enteredAutomobileProduction
Indicates that an entity began manufacturing automobiles as a commercial or industrial activity.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792cb9cc8190a7c45032427bca1a |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:21 p.m.