Triple
T32290358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forces Command |
E824948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | major formation of the Australian Army |
C15163
|
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: major formation of the Australian Army Context triple: [Forces Command, instanceOf, major formation of the Australian Army]
-
A.
Australian Army formation
chosen
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.
-
B.
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.
-
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.
formation of the South African Army
The formation of the South African Army refers to the historical process by which various colonial, Boer, and indigenous military forces were unified and organized into a single national land warfare branch under South African authority.
-
E.
Kitchener's Army formation
Kitchener's Army formation is a military unit composed of volunteer soldiers raised in response to Lord Kitchener's call for mass enlistment during World War I, typically organized into new divisions distinct from the pre-war regular army.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:44 a.m.