Triple
T14107240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guna traditional religion |
E339537
|
entity |
| Predicate | usesLanguage |
P238
|
FINISHED |
| Object | Guna language |
E68751
|
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: Guna language | Statement: [Guna traditional religion, usesLanguage, Guna language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guna language Context triple: [Guna traditional religion, usesLanguage, Guna language]
-
A.
Guna language
chosen
Guna language is an indigenous Chibchan language spoken by the Guna people of Panama and Colombia.
-
B.
Ganguela language
The Ganguela language is a Bantu language spoken by the Ganguela people of southwestern Africa, particularly in Angola.
-
C.
Gura language
The Gura language is an Ethiopian Semitic language spoken by the Gurage people in central Ethiopia.
-
D.
Gudu language
The Gudu language is a lesser-known Bantoid (Bena–Mboi) language spoken by a small ethnic community in northeastern Nigeria.
-
E.
Gonja language
The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600ada808190b92d67dc30f13d15 |
completed | April 14, 2026, 3:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0b699108190993f1102418ecff1 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:22 p.m.