Triple
T28414359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Canadian Ranger Patrol Group |
E719757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Ranger patrol group |
C54035
|
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 Ranger patrol group Context triple: [3rd Canadian Ranger Patrol Group, instanceOf, Canadian Ranger patrol group]
-
A.
Canadian militia infantry regiment
A Canadian militia infantry regiment is a part-time, citizen-soldier military unit organized to provide trained infantry forces for national defense, domestic operations, and support to the regular Canadian Army.
-
B.
Indian Band
An Indian Band is a musical ensemble originating from India that typically blends traditional Indian instruments and melodies with contemporary or classical musical styles to perform culturally rooted compositions.
-
C.
Apachean group
An Apachean group is a cultural and linguistic grouping of Native American peoples in the Athabaskan language family, including the Apache and Navajo, who share related languages, histories, and certain cultural traits.
-
D.
United States Army Indian Scouts unit
A United States Army Indian Scouts unit was a military formation composed primarily of Native American soldiers employed by the U.S. Army for their exceptional tracking, reconnaissance, and frontier warfare skills during the Indian Wars and beyond.
-
E.
Argentine National Gendarmerie
The Argentine National Gendarmerie is a federal security force responsible for border protection, rural and road safety, and supporting internal security operations across Argentina.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:29 a.m.