Triple
T2030615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Patricia's Canadian Light Infantry |
E44507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Army unit |
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: Canadian Army unit Context triple: [Princess Patricia's Canadian Light Infantry, instanceOf, Canadian Army unit]
-
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 United States Army
A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:38 p.m.