Triple
T30863746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 241st Engineering Installation Squadron |
E786134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering installation squadron |
C35523
|
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: engineering installation squadron Context triple: [241st Engineering Installation Squadron, instanceOf, engineering installation squadron]
-
A.
air engineering squadron
An air engineering squadron is a military unit responsible for the maintenance, repair, testing, and technical support of aircraft and related aerospace systems to ensure their operational readiness and safety.
-
B.
civil engineer squadron
chosen
A civil engineer squadron is a military unit responsible for planning, constructing, maintaining, and repairing infrastructure and facilities to support operational readiness and base sustainability.
-
C.
airborne engineer regiment
An airborne engineer regiment is a specialized military unit trained and equipped to deploy by air and conduct engineering tasks such as obstacle breaching, fortification, mobility, and infrastructure support in austere or contested environments.
-
D.
airlift squadron
An airlift squadron is a military aviation unit responsible for transporting personnel, equipment, and supplies by air to support operational, logistical, and humanitarian missions.
-
E.
aviation support battalion
An aviation support battalion is a military unit that provides maintenance, logistics, supply, and technical support to aviation brigades to ensure continuous, effective air operations.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:47 p.m.