Triple
T31598540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12th Light Horse Regiment |
E806283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Army light horse regiment |
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 light horse regiment Context triple: [12th Light Horse Regiment, instanceOf, Australian Army light horse regiment]
-
A.
Canadian Army cavalry regiment
A Canadian Army cavalry regiment is a military unit historically composed of mounted soldiers and now typically equipped with armored vehicles, responsible for reconnaissance, security, and mobile combat operations.
-
B.
Australian Imperial Force unit
An Australian Imperial Force unit is a military formation composed of Australian volunteer soldiers raised for overseas service during World War I under the Australian Imperial Force organization.
-
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.
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.
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.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:31 p.m.