Triple
T23696688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wutai Township |
E585467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountain indigenous township |
C46150
|
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: mountain indigenous township Context triple: [Wutai Township, instanceOf, mountain indigenous township]
-
A.
indigenous town
An indigenous town is a self-organized settlement primarily inhabited and governed by native peoples, reflecting their traditional social structures, cultural practices, and relationships to ancestral lands.
-
B.
indigenous township
chosen
An indigenous township is an administrative division or community area primarily inhabited and governed by indigenous peoples, often recognized for preserving their distinct cultural, social, and political practices within a broader national framework.
-
C.
mountain village
A mountain village is a small, often remote settlement nestled in or near mountainous terrain, characterized by close-knit communities, traditional architecture, and a lifestyle adapted to steep landscapes and variable climates.
-
D.
indigenous comarca
An indigenous comarca is a legally recognized territorial and administrative region governed by indigenous peoples, where they exercise cultural, political, and land rights according to their traditions and national law.
-
E.
indigenous community
An indigenous community is a group of people with historical continuity to pre-colonial or original inhabitants of a region, maintaining distinct cultural, social, and political traditions tied to their ancestral lands and identities.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:52 p.m.