Triple
T38202574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popé |
E1009106
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tewa person |
C63056
|
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: Tewa person Context triple: [Popé, instanceOf, Tewa person]
-
A.
Yámana person
A Yámana person is an individual belonging to the Indigenous Yámana (Yaghan) people of the southernmost regions of Tierra del Fuego, with cultural traditions deeply connected to maritime life and the harsh sub-Antarctic environment.
-
B.
Pima person
A Pima person is an individual belonging to the Pima (Akimel O’odham) Indigenous people, traditionally inhabiting the Gila and Salt River valleys of what is now Arizona, with a distinct language, culture, and social identity.
-
C.
Vedda person
A Vedda person is an individual belonging to the indigenous Vedda community of Sri Lanka, traditionally known for a forest-based, hunting-and-gathering lifestyle and distinct cultural and linguistic heritage.
-
D.
Cuman person
A Cuman person is an individual belonging to the medieval nomadic Turkic people known as the Cumans, who inhabited the Eurasian steppe and played a significant role in the history of Eastern Europe and Central Asia.
-
E.
Ladin person
A Ladin person is an individual belonging to the Ladin ethnic group of the Dolomite region in northern Italy, characterized by their distinct Rhaeto-Romance language and Alpine cultural traditions.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.