Triple
T29453713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VAAC Wellington |
E747043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation meteorology organization |
C656
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: aviation meteorology organization Context triple: [VAAC Wellington, instanceOf, aviation meteorology organization]
-
A.
meteorological organization
chosen
A meteorological organization is an entity responsible for observing, analyzing, and forecasting atmospheric conditions to support weather prediction, climate monitoring, and related public and scientific services.
-
B.
air navigation organization
An air navigation organization is an entity responsible for planning, managing, and controlling the safe and efficient movement of aircraft through designated airspace using air traffic services, communication, navigation, and surveillance systems.
-
C.
aviation infrastructure organization
An aviation infrastructure organization is an entity responsible for planning, developing, operating, and maintaining the physical and technological systems that support air transportation, such as airports, air traffic control, and related facilities.
-
D.
aviation authority
An aviation authority is a governmental or regulatory body responsible for overseeing civil aviation safety, security, standards, and compliance within a specific jurisdiction.
-
E.
aviation rating organization
An aviation rating organization is an entity that evaluates, certifies, and assigns performance or safety ratings to aviation-related operations, personnel, or equipment based on established standards and regulatory criteria.
- F. None of above.
Provenance (1 batch)
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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:34 p.m.