Triple
T8670046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-28A Draco |
E205771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special operations aircraft |
C2492
|
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: special operations aircraft Context triple: [U-28A Draco, instanceOf, special operations aircraft]
-
A.
special operations aviation regiment
A special operations aviation regiment is a military aviation unit specialized in providing highly trained air support, insertion, extraction, and logistical capabilities for special operations forces in complex and high-risk environments.
-
B.
special operations aviation command
A special operations aviation command is a military organization that provides specialized, often clandestine air support—such as infiltration, exfiltration, resupply, and close air support—for special operations forces in high-risk or sensitive missions.
-
C.
military aircraft
chosen
A military aircraft is a powered flying vehicle specifically designed, equipped, and operated by armed forces to conduct combat, support, reconnaissance, or training missions in defense and warfare operations.
-
D.
reconnaissance aircraft
A reconnaissance aircraft is a specialized military or intelligence-gathering airplane designed to observe, monitor, and collect information about enemy forces, terrain, or strategic targets using advanced sensors and surveillance equipment.
-
E.
strategic airlifter
A strategic airlifter is a large military transport aircraft designed to carry heavy cargo, troops, and equipment over long distances to support global deployment and sustainment 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.