Triple
T6851956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas City Southern Railway |
E158040
|
entity |
| Predicate | coreNetworkLinked |
P65111
|
FINISHED |
| Object | U.S. Midwest |
—
|
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: U.S. Midwest | Statement: [Kansas City Southern Railway, coreNetworkLinked, U.S. Midwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreNetworkLinked Context triple: [Kansas City Southern Railway, coreNetworkLinked, U.S. Midwest]
-
A.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
B.
networkPartOf
Indicates that one network is a component or subdivision of a larger, encompassing network.
-
C.
branchNetwork
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of another entity.
-
D.
sharesBorderingNetworkWith
Indicates that two entities are connected through adjacent or directly neighboring positions within the same network structure.
-
E.
operatedInNetwork
chosen
Indicates that an entity carried out its activities or services within a specified network or system.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84e6fb08190915954be5b0df2d8 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.