Triple
T36275591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Aeronautics (CDOT) |
E892798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation agency |
C1857
|
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 agency Context triple: [Division of Aeronautics (CDOT), instanceOf, aviation agency]
-
A.
aviation authority
chosen
An aviation authority is a governmental or regulatory body responsible for overseeing civil aviation safety, security, standards, and compliance within a specific jurisdiction.
-
B.
government aviation unit
A government aviation unit is an official organizational entity that operates and manages aircraft to support public missions such as law enforcement, emergency response, transportation, surveillance, and other governmental functions.
-
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 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.
-
E.
aviation standards organization
An aviation standards organization is an entity that develops, maintains, and promotes technical, safety, and operational standards to ensure interoperability, reliability, and safety across the aviation industry.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.