Triple
T4022720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Australian Electrical and Mechanical Engineers |
E91315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Army corps |
C297
|
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 corps Context triple: [Royal Australian Electrical and Mechanical Engineers, instanceOf, Australian Army corps]
-
A.
airborne corps
An airborne corps is a large military formation composed primarily of paratrooper and air-transportable units, organized and equipped to conduct large-scale airborne operations behind or across enemy lines.
-
B.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
C.
armoured corps
An armoured corps is a large military formation composed primarily of tank and mechanized units, designed to deliver rapid, heavily protected offensive and defensive ground operations.
-
D.
land warfare service branch
chosen
A land warfare service branch is a military organization primarily responsible for conducting combat and support operations on land using ground forces and associated assets.
-
E.
Canadian Armed Forces sub-component
A Canadian Armed Forces sub-component is a distinct organizational element within the Canadian military structure, such as a specific command, formation, or unit, that performs defined roles and responsibilities in support of national defense objectives.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:35 p.m.