Triple
T10909608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiwiar |
E257659
|
entity |
| Predicate | relatedPeople |
P37
|
FINISHED |
| Object | Shuar |
E8615
|
NE FINISHED |
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: Shuar | Statement: [Shiwiar, relatedPeople, Shuar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shuar Context triple: [Shiwiar, relatedPeople, Shuar]
-
A.
Shuar
chosen
Shuar is an indigenous language of the Jivaroan family spoken by the Shuar people primarily in the Amazonian regions of Ecuador and Peru.
-
B.
Shua
Shua is a biblical figure mentioned in genealogical records as a sibling of Shobab.
-
C.
Shuar Chicham
Shuar Chicham is the indigenous language of the Shuar people of the Ecuadorian Amazon, belonging to the Jivaroan language family.
-
D.
Sarju
Sarju is an alternate name for the Sarayu, a river historically associated with the ancient Indian city of Ayodhya and revered in Hindu tradition.
-
E.
Shuru
Shuru is a dialect of the Berta language spoken by the Berta people of the Ethiopia–Sudan border region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77068e5488190bbc881ebf51d6b2e |
completed | April 9, 2026, 9:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a92e09648190ab39053521211743 |
completed | April 18, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:22 p.m.