Triple
T30291058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Australian Air Force Security Forces |
E770374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground defence unit |
C2497
|
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: ground defence unit Context triple: [Royal Australian Air Force Security Forces, instanceOf, ground defence unit]
-
A.
regional military unit
A regional military unit is an organized group of armed forces assigned to operate within a specific geographic area, responsible for defense, security, and military operations in that region.
-
B.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
air and missile defence force
An air and missile defence force is a military organization responsible for detecting, tracking, and intercepting hostile aircraft and missiles to protect designated airspace, forces, and critical assets.
-
D.
Japan Ground Self-Defense Force unit
A Japan Ground Self-Defense Force unit is an organized, mission-specific formation of personnel and equipment within Japan’s land-based military, structured to conduct defense, security, and support operations under national and international mandates.
-
E.
ground-based air defense system
A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:47 p.m.