Triple
T11242632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skytrax Best North American Airport |
E266107
|
entity |
| Predicate | surveyPopulation |
P42127
|
FINISHED |
| Object | airline passengers |
—
|
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: airline passengers | Statement: [Skytrax Best North American Airport, surveyPopulation, airline passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveyPopulation Context triple: [Skytrax Best North American Airport, surveyPopulation, airline passengers]
-
A.
surveyFunction
Indicates that an entity serves as a survey-related function or role in relation to another entity or context.
-
B.
surveyedIn
chosen
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
C.
administrationPopulation
Indicates the total number of people living within the jurisdiction or area governed by a particular administrative unit.
-
D.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
E.
surveyMethod
Indicates the technique or procedure used to conduct a survey or collect survey data.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e91b0b808190bc38008bb344d180 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.