Triple

T3272728
Position Surface form Disambiguated ID Type / Status
Subject Xizhimen station E68686 entity
Predicate servesTransportMode P1379 FINISHED
Object urban rail transit 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: urban rail transit | Statement: [Xizhimen station, servesTransportMode, urban rail transit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesTransportMode
Context triple: [Xizhimen station, servesTransportMode, urban rail transit]
  • A. transportationServedBy
    Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
  • B. publicTransitMode
    Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
  • C. appliesToTransportMode
    Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular mode of transport.
  • D. transportType chosen
    Indicates the mode or means of transportation used in carrying something or someone from one place to another.
  • E. isPublicTransport
    Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
  • 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_69ad859b54f881909bf530d549caf2fd completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adaff6308881908886a44804a0bb09 completed March 8, 2026, 5:20 p.m.
PD Predicate disambiguation batch_69ada420167c81909b6e2702db296d9e completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:10 p.m.