Triple
T30260659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 37 Squadron RAAF |
E769481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military transport squadron |
C29707
|
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 transport squadron Context triple: [No. 37 Squadron RAAF, instanceOf, military transport squadron]
-
A.
airlift squadron
chosen
An airlift squadron is a military aviation unit responsible for transporting personnel, equipment, and supplies by air to support operational, logistical, and humanitarian missions.
-
B.
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.
-
C.
Air Force squadron
An Air Force squadron is a military aviation unit composed of multiple aircraft and personnel, organized to perform specific operational, training, or support missions under a unified command.
-
D.
air refueling squadron
An air refueling squadron is a military aviation unit equipped and trained to provide in-flight refueling support to extend the range, endurance, and operational flexibility of airborne aircraft.
-
E.
Marine Air-Ground Task Force logistics element
The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:41 p.m.