Triple
T1336200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri–Kansas–Texas Railroad |
E28754
|
entity |
| Predicate | enteredIndianTerritory |
P14234
|
FINISHED |
| Object | 1870 |
—
|
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: 1870 | Statement: [Missouri–Kansas–Texas Railroad, enteredIndianTerritory, 1870]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredIndianTerritory Context triple: [Missouri–Kansas–Texas Railroad, enteredIndianTerritory, 1870]
-
A.
endedInTerritory
Indicates that an event or action concluded within the bounds of a specified territory or geographic area.
-
B.
declaresIndiaAs
Indicates that a subject formally designates or proclaims something or someone as India.
-
C.
cameIntoForceInCountry
Indicates that a law, regulation, or agreement became legally effective within a specified country.
-
D.
enteredSpace
chosen
Indicates that an entity has moved into or crossed the boundary into a particular space or area.
-
E.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1ecb5208190a9eadda113c91e66 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.