Triple
T22293688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 309th Aerospace Maintenance and Regeneration Group |
E551063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft storage and maintenance organization |
C21860
|
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: aircraft storage and maintenance organization Context triple: [309th Aerospace Maintenance and Regeneration Group, instanceOf, aircraft storage and maintenance organization]
-
A.
aircraft maintenance company
An aircraft maintenance company is an organization that inspects, repairs, overhauls, and services aircraft and their components to ensure safety, reliability, and regulatory compliance.
-
B.
military aviation maintenance organization
chosen
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.
-
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.
aircraft hangar
An aircraft hangar is a large, enclosed structure designed for housing, maintaining, and protecting aircraft from weather and environmental conditions.
-
E.
aircraft disassembly company
A company that specializes in safely decommissioning, dismantling, and recycling aircraft and their components at the end of their operational life.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:41 p.m.