Triple
T35429949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Cancun |
E1024027
|
entity |
| Predicate | majorAirportInZone |
P281
|
FINISHED |
| Object | Cancún International Airport |
—
|
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: Cancún International Airport | Statement: [America/Cancun, majorAirportInZone, Cancún International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorAirportInZone Context triple: [America/Cancun, majorAirportInZone, Cancún International Airport]
-
A.
largerAirportInArea
Indicates that one airport is the larger airport within a specified geographic area or region.
-
B.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
C.
otherMajorAirportInRegion
Indicates that the subject airport is a different major airport located within the same geographic region as the object airport.
-
D.
hasMajorAirport
chosen
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
E.
mainAccessAirport
Indicates that one location serves as the primary airport providing access to another place or region.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:03 p.m.