Triple
T28852447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 34 Canadian Brigade Group |
E728637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Army brigade group |
C10837
|
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: Canadian Army brigade group Context triple: [34 Canadian Brigade Group, instanceOf, Canadian Army brigade group]
-
A.
Canadian Army formation
chosen
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.
-
B.
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.
-
C.
U.S. Army infantry brigade
A U.S. Army infantry brigade is a modular, combined-arms combat unit typically consisting of several infantry battalions and supporting elements, organized to conduct sustained ground operations across a range of missions.
-
D.
U.S. Army task force
A U.S. Army task force is a temporary, mission-tailored organization composed of units from different branches and echelons, formed to accomplish a specific operational objective.
-
E.
U.S. Army brigade combat team
A U.S. Army brigade combat team is a modular, self-sustaining combined-arms formation, typically 3,000–5,000 soldiers, designed to conduct independent, full-spectrum operations as the Army’s primary tactical warfighting unit.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:44 a.m.