Triple
T22181228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal New Zealand Infantry Regiment |
E548172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regiment of the New Zealand Army |
C22733
|
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: regiment of the New Zealand Army Context triple: [Royal New Zealand Infantry Regiment, instanceOf, regiment of the New Zealand Army]
-
A.
New Zealand Army formation
chosen
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 position
A New Zealand Army position is a specific role or appointment within the New Zealand Army that defines an individual's rank, responsibilities, duties, and place in the military hierarchy.
-
C.
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.
-
D.
reconnaissance regiment
A reconnaissance regiment is a military unit specialized in gathering intelligence on enemy forces and terrain, typically using mobility, stealth, and advanced surveillance equipment to support larger formations.
-
E.
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.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.