Triple
T17159657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 51 FNQR |
E416443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Army Reserve 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 Reserve infantry battalion Context triple: [51 FNQR, instanceOf, Australian Army Reserve infantry battalion]
-
A.
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.
-
B.
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.
-
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.
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.
-
E.
Primary Reserve infantry regiment
A Primary Reserve infantry regiment is a part-time, volunteer military unit that provides trained infantry soldiers to support and augment a nation's regular army during operations, emergencies, and domestic tasks.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.