Triple

T6785772
Position Surface form Disambiguated ID Type / Status
Subject Kansas City Southern de México E155797 entity
Predicate hasCrossBorderService P66819 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: [Kansas City Southern de México, hasCrossBorderService, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCrossBorderService
Context triple: [Kansas City Southern de México, hasCrossBorderService, yes]
  • A. servesCrossBorderArea chosen
    Indicates that a service, activity, or function extends beyond a single jurisdiction and operates across national or regional borders.
  • B. hasCrossBorderManagement
    Indicates that an entity exercises management or control over operations, assets, or activities that extend across national borders.
  • C. hasBorderCrossingFunction
    Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
  • D. hasCrossBorderTourism
    Indicates that there is tourism activity involving travel across national or regional borders between the related entities.
  • E. hasBorderCrossing
    Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
  • 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_69c6881770fc8190972b2906390380f5 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d28f043081909a9a9ab635785933 completed March 27, 2026, 6:55 p.m.
PD Predicate disambiguation batch_69c6d0979ce0819094678896da4e3169 completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:14 p.m.