Triple
T16290121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NZNP |
E395495
|
entity |
| Predicate | servesAirCargoTraffic |
P99377
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NZNP, servesAirCargoTraffic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAirCargoTraffic Context triple: [NZNP, servesAirCargoTraffic, true]
-
A.
airTransportServedBy
Indicates that a particular air transport service (such as a route, flight, or airport operation) is provided or operated by a specified carrier or service provider.
-
B.
handlesCargoTraffic
chosen
Indicates that an entity is responsible for managing or processing the movement of cargo traffic.
-
C.
servesAirportICAO
Indicates that a transportation service or facility operates routes to or from the airport identified by the given ICAO code.
-
D.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
-
E.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e249175e24819082e571039e278056 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.