Triple

T1959612
Position Surface form Disambiguated ID Type / Status
Subject MMMX E42350 entity
Predicate hasPassengerTrafficRankInLatinAmerica P34408 FINISHED
Object one of the busiest 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: one of the busiest | Statement: [MMMX, hasPassengerTrafficRankInLatinAmerica, one of the busiest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPassengerTrafficRankInLatinAmerica
Context triple: [MMMX, hasPassengerTrafficRankInLatinAmerica, one of the busiest]
  • A. hasPassengerTrafficRank
    Indicates the relative position or ranking of an entity based on the volume of passenger traffic it handles compared to others.
  • B. peakPassengerTrafficRank
    Indicates the relative position of an entity in an ordered list based on the amount of passenger traffic it experiences at its peak.
  • C. passengerTrafficRankUS
    Indicates the relative ranking of a location or facility within the United States based on the volume of passenger traffic it handles.
  • D. passengerTrafficRankingWorld
    Indicates the relative position of an entity in a global ranking based on the volume of passenger traffic it handles.
  • E. hasApproxAnnualPassengerUsageRank
    Indicates the approximate position or ranking of an entity based on its annual passenger usage compared to similar entities.
  • F. None of above. chosen

Provenance (4 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_69a8870eea088190a38781990812a9bc completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb68a8e608190bc37a85913b3cd44 completed March 7, 2026, 5:24 a.m.
PD Predicate disambiguation batch_69abaff5dbd48190a9d36ca60de151db completed March 7, 2026, 4:56 a.m.
PDg Predicate description generation batch_69abb6893eb881908923f0168374596a completed March 7, 2026, 5:24 a.m.
Created at: March 4, 2026, 7:36 p.m.