Triple
T26522323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2/22nd Battalion |
E669989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Army infantry battalion |
C15162
|
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 infantry battalion Context triple: [2/22nd Battalion, instanceOf, Australian Army infantry battalion]
-
A.
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.
-
B.
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.
-
C.
component of the Australian Army
chosen
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.
Territorial Army battalion
A Territorial Army battalion is a reserve military unit composed of part-time volunteer soldiers who train periodically and can be mobilized to support regular forces in national defense, security operations, and emergencies.
-
E.
U.S. Army battalion
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:28 a.m.