Triple
T15765415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centrair |
E382206
|
entity |
| Predicate | annualPassengerTrafficCategory |
P27830
|
FINISHED |
| Object | major |
—
|
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: major | Statement: [Centrair, annualPassengerTrafficCategory, major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualPassengerTrafficCategory Context triple: [Centrair, annualPassengerTrafficCategory, major]
-
A.
hasAnnualPassengerTrafficOver
Indicates that the subject location or transport facility experiences an annual passenger volume exceeding a specified threshold.
-
B.
passengerTraffic
Indicates the flow or volume of passengers moving through or using a particular transport service, route, or facility.
-
C.
servesPassengerTrafficType
chosen
Indicates that a transportation facility or service accommodates a specified type or category of passenger traffic.
-
D.
hasPassengerTrafficRank
Indicates the relative position or ranking of an entity based on the volume of passenger traffic it handles compared to others.
-
E.
peakPassengerTrafficRank
Indicates the relative position of an entity in an ordered list based on the amount of passenger traffic it experiences at its peak.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b8154881908afe5191e6424f15 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.