Triple
T19976342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Test and Evaluation Squadron 31 |
E493700
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air test and evaluation squadron |
C37071
|
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: air test and evaluation squadron Context triple: [Air Test and Evaluation Squadron 31, instanceOf, air test and evaluation squadron]
-
A.
test and evaluation squadron
chosen
A test and evaluation squadron is a military aviation unit responsible for planning, conducting, and analyzing tests of aircraft, weapons, and related systems to validate performance, safety, and operational effectiveness.
-
B.
air control squadron
An air control squadron is a military unit responsible for providing radar surveillance, airspace management, and command and control of aircraft within a designated area of operations.
-
C.
airborne early warning squadron
An airborne early warning squadron is a military aviation unit equipped with specialized radar aircraft to detect, track, and relay information on aerial and surface threats, providing command and control support to friendly forces.
-
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.
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.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:26 p.m.