Triple
T30397943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence of Australia (World War II) |
E773271
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian military history topic |
C22322
|
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 military history topic Context triple: [Defence of Australia (World War II), instanceOf, Australian military history topic]
-
A.
Australian historical event
chosen
An Australian historical event is a significant occurrence in Australia’s past that has shaped the nation’s political, social, cultural, or economic development.
-
B.
Australian Defence Force position
An Australian Defence Force position represents a specific role or appointment within the ADF’s organizational structure, defined by its responsibilities, rank requirements, and placement in the command hierarchy.
-
C.
Australian Army barracks
An Australian Army barracks is a military facility that provides accommodation, training areas, administrative offices, and support services for Australian Army personnel and units.
-
D.
Australian Army formation
An Australian Army formation is a structured military organization composed of multiple units and sub-units, established to plan, coordinate, and conduct land operations under a unified command within the Australian Army.
-
E.
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.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:03 p.m.