Triple
T15985534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of Army (New Zealand) |
E387682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New Zealand Army position |
C36787
|
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: New Zealand Army position Context triple: [Chief of Army (New Zealand), instanceOf, New Zealand Army position]
-
A.
New Zealand Army formation
A New Zealand Army formation is an organized military unit or grouping, such as a brigade or division, composed of personnel and equipment structured to conduct land operations under a unified command.
-
B.
New Zealand Army officer
A New Zealand Army officer is a commissioned leader in New Zealand’s land warfare branch, responsible for commanding soldiers, planning and executing military operations, and upholding the defense and security objectives of New Zealand.
-
C.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
D.
Indian Army position
An Indian Army position is a specific rank or role within the organizational hierarchy of the Indian Army, defining an individual's authority, responsibilities, and duties in military operations and administration.
-
E.
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.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.