Triple
T37636673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tissahamy |
E936506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vedda person |
C62552
|
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: Vedda person Context triple: [Tissahamy, instanceOf, Vedda 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.
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.
-
C.
Veda
Veda is a conceptual class representing a comprehensive body of sacred or foundational knowledge that serves as an authoritative source for understanding and guiding a particular domain or system.
-
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.
Tangut person
A Tangut person is an individual belonging to the Tangut ethnic group, historically associated with the Western Xia dynasty and characterized by their distinct language, script, and cultural traditions in northwestern China.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.