Triple
T30074993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Wootten – Australian forces |
E764293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian military contingent |
C56687
|
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 contingent Context triple: [George Wootten – Australian forces, instanceOf, Australian military contingent]
-
A.
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.
-
B.
Polish military contingent
A Polish military contingent is a temporary, organized group of Polish Armed Forces personnel and resources deployed for specific missions, operations, or international commitments.
-
C.
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.
-
D.
Australian Army reserve unit
An Australian Army reserve unit is a part-time military formation composed of trained civilian volunteers who support the Australian Defence Force’s operational, training, and domestic response capabilities.
-
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. chosen
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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:01 p.m.