Triple
T24905984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KCS |
E623708
|
entity |
| Predicate | railroadHeadquarteredIn |
P149455
|
FINISHED |
| Object | Kansas City, Missouri |
—
|
NE NERFINISHED |
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: Kansas City, Missouri | Statement: [KCS, railroadHeadquarteredIn, Kansas City, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadHeadquarteredIn Context triple: [KCS, railroadHeadquarteredIn, Kansas City, Missouri]
-
A.
headquartersRailroadCity
chosen
Indicates that a railroad company has its main headquarters located in a particular city.
-
B.
hasRailwayHeadquarters
Indicates that a railway organization or system has its main administrative or operational headquarters located at a specified place.
-
C.
relatedRailroad
Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
-
D.
railwayDivisionHeadquartersOf
Indicates that one location serves as the administrative headquarters for a specified railway division.
-
E.
foundedAsRailroadStopFor
Indicates that one place or settlement was originally established specifically to serve as a railroad stop for another location or line.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:27 a.m.