Triple
T2549146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Engineers |
E57977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corps 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: corps of the Canadian Army Context triple: [Royal Canadian Engineers, instanceOf, corps of the Canadian Army]
-
A.
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.
-
B.
Canadian Expeditionary Force formation
A Canadian Expeditionary Force formation is an organized military unit or grouping, such as a battalion, brigade, or division, raised by Canada for overseas service during the First World War.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:47 p.m.