Triple
T1986569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Machine Gun Corps |
E43154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Army formation |
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 formation Context triple: [Canadian Machine Gun Corps, instanceOf, Canadian Army formation]
-
A.
United States Army formation type
A United States Army formation type is a standardized organizational structure that defines the size, composition, and command hierarchy of Army units for specific operational roles and missions.
-
B.
United States military formation
A United States military formation is an organized grouping of U.S. armed forces personnel and units, structured and deployed to conduct specific missions or operations under a defined command hierarchy.
-
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.
United States Army army group
A United States Army army group is a large, high-level operational formation composed of multiple field armies, organized to conduct major theater-wide campaigns under a single strategic command.
-
E.
United States Army position
A United States Army position is a specific role or job within the Army’s organizational structure, defined by rank, responsibilities, and duties in support of military operations and administration.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.