Triple
T34513864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whenuapai Airport |
E886094
|
entity |
| Predicate | usedAsMainInternationalAirportFor |
P120245
|
FINISHED |
| Object | Auckland |
—
|
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: Auckland | Statement: [Whenuapai Airport, usedAsMainInternationalAirportFor, Auckland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMainInternationalAirportFor Context triple: [Whenuapai Airport, usedAsMainInternationalAirportFor, Auckland]
-
A.
isOnlyInternationalAirportOf
Indicates that an airport is the single, unique international airport serving a particular city, region, or country.
-
B.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
C.
hasPrimaryAirportRole
chosen
Indicates that an entity holds the main or principal functional role associated with an airport.
-
D.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
E.
replacedAsMainAirportFor
Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 2:01 a.m.