Triple
T33879382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil aviation authorities |
E868443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation regulator type |
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 regulator type Context triple: [Civil aviation authorities, instanceOf, aviation regulator type]
-
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.
aircraft type
An aircraft type is a classification of aircraft sharing the same basic design, performance characteristics, and operational capabilities, typically defined by a manufacturer and certified as a distinct model.
-
C.
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.
-
D.
aviation regulatory decision
An aviation regulatory decision is an authoritative ruling or policy issued by a competent aviation authority that defines, interprets, or enforces rules governing the safety, operation, certification, or oversight of civil aviation activities.
-
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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.