Triple
T35103747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juruá River region |
E1013090
|
entity |
| Predicate | partOfAncestralHomelandOf |
P202380
|
FINISHED |
| Object | Asháninka people |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Asháninka people | Statement: [Juruá River region, partOfAncestralHomelandOf, Asháninka people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfAncestralHomelandOf Context triple: [Juruá River region, partOfAncestralHomelandOf, Asháninka people]
-
A.
recognizedAsAncestralNationOf
Indicates that one entity is formally acknowledged or regarded as the ancestral homeland or originating nation of another entity.
-
B.
usedToBeHomelandOf
Indicates that a place previously served as the homeland or native territory of a particular group or entity, but no longer does so.
-
C.
primaryAncestralCountry
Indicates the country that is considered the main place of origin for an individual’s or group’s ancestors.
-
D.
countryOfDiaspora
Indicates the country in which a diaspora community originating from another place is located.
-
E.
countryOfHeritage
Indicates the country from which an entity’s cultural, ancestral, or familial heritage originates.
- F. None of above. chosen
Provenance (4 batches)
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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
| PDg | Predicate description generation | batch_6a00781ac0f48190a77e2c326a4d6693 |
completed | May 10, 2026, 12:20 p.m. |
Created at: May 3, 2026, 4:01 p.m.