Triple
T20604696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gitlaxt’aamiks |
E506273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | settlement in British Columbia |
C43340
|
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: settlement in British Columbia Context triple: [Gitlaxt’aamiks, instanceOf, settlement in British Columbia]
-
A.
settlement in Nunavut
A settlement in Nunavut is a small, often remote community within Canada's northern territory, typically characterized by predominantly Inuit populations, limited infrastructure, and reliance on local resources and traditional lifestyles.
-
B.
settlement in Scotland
A settlement in Scotland is any inhabited place, ranging from small hamlets and villages to towns and cities, recognized as a distinct community within the country’s geographic and administrative landscape.
-
C.
settlement in England
A settlement in England is a community where people live, ranging from small hamlets and villages to larger towns and cities, defined by its inhabited area and local infrastructure within the country of England.
-
D.
settlement in Japan
A settlement in Japan is a geographically defined inhabited place, such as a city, town, village, or hamlet, recognized within Japan’s administrative and cultural landscape as a distinct community where people live and interact.
-
E.
land claims settlement
A land claims settlement is a formal agreement that resolves disputes over land ownership or use rights, typically between governments and Indigenous or local communities, through compensation, land transfers, or legal recognition of rights.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.