Triple
T24468243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Air Standards Coordinating Committee |
E617031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aviation standards body |
C2464
|
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: military aviation standards body Context triple: [NATO Air Standards Coordinating Committee, instanceOf, military aviation standards body]
-
A.
military aviation maintenance organization
A military aviation maintenance organization is a structured unit responsible for inspecting, repairing, servicing, and ensuring the airworthiness and mission readiness of military aircraft and related systems.
-
B.
military standard
chosen
A military standard is an officially established set of technical, procedural, or quality requirements used by armed forces to ensure compatibility, reliability, and uniformity of equipment, systems, and practices.
-
C.
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.
-
D.
military aviation command
A military aviation command is an organizational unit responsible for planning, directing, coordinating, and controlling the employment, readiness, and support of air forces to achieve strategic and operational military objectives.
-
E.
military air transport organization
A military air transport organization is a structured entity responsible for planning, coordinating, and executing the airlift of personnel, equipment, and supplies to support military operations and strategic objectives.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:20 a.m.