Triple
T22778656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAA Part 23 |
E563773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States federal aviation regulation |
C4625
|
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: United States federal aviation regulation Context triple: [FAA Part 23, instanceOf, United States federal aviation regulation]
-
A.
aviation regulatory framework
The aviation regulatory framework is the structured set of laws, standards, and oversight mechanisms that govern the safe, efficient, and environmentally responsible operation of civil aviation activities.
-
B.
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.
-
C.
aviation law
chosen
Aviation law is the body of rules, regulations, and international agreements that govern the operation, safety, security, and economic aspects of air travel and aircraft use.
-
D.
Federal Aviation Administration publication
A Federal Aviation Administration publication is an official document issued by the FAA that provides regulations, standards, procedures, guidance, or informational material related to civil aviation safety and operations in the United States.
-
E.
European Union aviation safety document
A European Union aviation safety document is an official regulatory or guidance text issued by EU institutions or agencies that sets standards, procedures, and requirements to ensure the safety of civil aviation operations within EU airspace and by EU operators.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:28 p.m.