Triple

T38516518
Position Surface form Disambiguated ID Type / Status
Subject Tacubaya metro station E922354 entity
Predicate isMajorInterchangeHub P190500 FINISHED
Object true 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: true | Statement: [Tacubaya metro station, isMajorInterchangeHub, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMajorInterchangeHub
Context triple: [Tacubaya metro station, isMajorInterchangeHub, true]
  • A. isMajorInterchangeFor
    Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
  • B. isMajorBusHub
    Indicates that a location serves as a primary node in the bus network, with high connectivity and significant passenger or route volume.
  • C. isMajorTransferHubIn chosen
    Indicates that a location functions as a primary node where significant volumes of transfers or connections occur within a specified area or network.
  • D. hasMajorHubIn
    Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
  • E. hasMajorCityHub
    Indicates that an entity contains or is associated with a primary, high-importance city that functions as a central hub for activity, services, or connectivity.
  • 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_69f76ea5f5588190bd0b28c82e975640 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69febce5877c8190a5e000ef5331ec88 completed May 9, 2026, 4:49 a.m.
PD Predicate disambiguation batch_69febad1cd588190abc7686bcb39a371 completed May 9, 2026, 4:40 a.m.
Created at: May 3, 2026, 4:32 p.m.