Triple
T2043714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal 22e Régiment |
E45402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regiment of the Canadian Army |
C2497
|
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 Canadian Army Context triple: [Royal 22e Régiment, instanceOf, regiment of the Canadian Army]
-
A.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
component of the Royal Canadian Air Force
A component of the Royal Canadian Air Force is an organizational subdivision, such as a command, wing, squadron, or unit, that performs specific operational, support, or administrative functions within the RCAF structure.
-
C.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
-
D.
land warfare service branch
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.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:39 p.m.