Triple
T29118711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 114 Mobile Control and Reporting Unit RAAF |
E737116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air control and reporting unit |
C26150
|
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 control and reporting unit Context triple: [No. 114 Mobile Control and Reporting Unit RAAF, instanceOf, air control and reporting unit]
-
A.
deployable air command and control centre
A deployable air command and control centre is a mobile, rapidly configurable facility that provides the infrastructure, systems, and personnel needed to plan, direct, and coordinate air operations in a given theater.
-
B.
air advisory unit
An air advisory unit is a specialized military or governmental team that provides expert guidance, planning, and support to partner air forces to enhance their operational, technical, and organizational capabilities.
-
C.
air control squadron
chosen
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.
-
D.
air traffic control tower
A structure at an airport from which air traffic controllers monitor and direct aircraft movements on the ground and in the airspace around the airport to ensure safe and efficient operations.
-
E.
aviation support unit
An aviation support unit is an organizational entity that provides maintenance, logistics, ground handling, and operational assistance to ensure the effective and safe functioning of aircraft and flight 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 11:24 a.m.