Triple
T30764807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago FSDO |
E783337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Flight Standards District Office |
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: Flight Standards District Office Context triple: [Chicago FSDO, instanceOf, Flight Standards District Office]
-
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.
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.
-
C.
flight test center
A flight test center is a specialized facility where aircraft, spacecraft, or related systems are systematically tested, evaluated, and validated under controlled conditions to ensure performance, safety, and regulatory compliance.
-
D.
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.
-
E.
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.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:39 p.m.