Triple
T10902138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jivaroan languages |
E257471
|
entity |
| Predicate | hasNotableLanguage |
P7390
|
FINISHED |
| Object | Huambisa language |
E896181
|
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: Huambisa language | Statement: [Jivaroan languages, hasNotableLanguage, Huambisa language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Huambisa language Context triple: [Jivaroan languages, hasNotableLanguage, Huambisa language]
-
A.
Huambisa language
chosen
The Huambisa language is an indigenous Jivaroan language spoken by the Huambisa (Wampis) people of the northern Peruvian Amazon.
-
B.
Sipakapense language
The Sipakapense language is a Mayan language spoken by the Sipakapense people in the western highlands of Guatemala.
-
C.
Mampruli language
Mampruli is a Gur language spoken primarily by the Mamprusi people in northern Ghana and parts of neighboring West African countries.
-
D.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
E.
Bitama language
The Bitama language is a lesser-known Nilo-Saharan language spoken by a subgroup of the Kunama people in the Horn of Africa.
- 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_69d761a3e83c81908dc48c0fb7935da7 |
completed | April 9, 2026, 8:21 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.