Triple
T1336222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri–Kansas–Texas Railroad |
E28754
|
entity |
| Predicate | operatedInIndianTerritory |
P6665
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Missouri–Kansas–Texas Railroad, operatedInIndianTerritory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInIndianTerritory Context triple: [Missouri–Kansas–Texas Railroad, operatedInIndianTerritory, yes]
-
A.
operatedInRegion
chosen
Indicates that an entity conducted operations or activities within a specified geographic region.
-
B.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
C.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
D.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
-
E.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
- 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.