Triple
T33504270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeronautical Charts |
E858072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aviation chart |
C22399
|
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 chart Context triple: [Aeronautical Charts, instanceOf, Aviation chart]
-
A.
aeronautical information publication
An aeronautical information publication is an official, regularly issued document that provides essential, long-term aeronautical information necessary for the safety, regularity, and efficiency of air navigation within a specific state or region.
-
B.
aeronautical information product
chosen
An aeronautical information product is a compiled and formatted set of aviation-related data (such as charts, publications, and digital datasets) designed to support the safe and efficient planning, execution, and management of air navigation.
-
C.
aviation challenge
An aviation challenge is a competitive or problem-solving event that tests participants’ skills, knowledge, and innovation in aircraft operation, design, navigation, or related aeronautical disciplines.
-
D.
aviation infrastructure network
An aviation infrastructure network is an interconnected system of airports, airways, navigation aids, communication systems, and support facilities that collectively enable the safe, efficient movement of aircraft and passengers.
-
E.
aviation attraction
An aviation attraction is a location, exhibit, or experience designed to engage visitors with aircraft, flight history, and aeronautical technology through displays, demonstrations, or interactive activities.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.