Triple
T16741191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Aviation Regiment |
E406837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Army aviation regiment |
C23740
|
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: Australian Army aviation regiment Context triple: [1st Aviation Regiment, instanceOf, Australian Army aviation regiment]
-
A.
Royal Australian Air Force unit
A Royal Australian Air Force unit is an organizational entity within the RAAF, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support roles in air and space power.
-
B.
Royal Australian Air Force wing
A Royal Australian Air Force wing is a major operational or support formation comprising multiple squadrons and units, responsible for coordinating and delivering specific air power capabilities within the RAAF.
-
C.
component of the Australian Army
A component of the Australian Army is an organizational subdivision—such as a unit, formation, corps, or support element—that contributes specific capabilities and functions to the Army’s overall mission and operations.
-
D.
army aviation unit
chosen
An army aviation unit is a military organization equipped with rotary- and/or fixed-wing aircraft to provide reconnaissance, air assault, transport, close air support, and other aviation capabilities in support of ground forces.
-
E.
Royal Australian Air Force unit elements
Royal Australian Air Force unit elements are the organizational components—such as squadrons, wings, and support units—that structure, operate, and sustain the RAAF’s air power capabilities.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.