Triple
T16617360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beti-Pahuin peoples |
E403728
|
entity |
| Predicate | languageGroup |
P3349
|
FINISHED |
| Object | Beti language |
E87001
|
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: Beti language | Statement: [Beti-Pahuin peoples, languageGroup, Beti language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beti language Context triple: [Beti-Pahuin peoples, languageGroup, Beti language]
-
A.
Beti languages
chosen
The Beti languages are a group of closely related Bantu languages spoken primarily in Cameroon, Equatorial Guinea, and neighboring regions of Central Africa.
-
B.
Buyi language
The Buyi language is a Tai–Kadai language spoken primarily by the Buyi ethnic group in Guizhou and neighboring regions of southern China.
-
C.
Bafia language
The Bafia language is a Bantu language spoken primarily by the Bafia people in central Cameroon.
-
D.
Belhare language
The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
-
E.
Mangbetu language
The Mangbetu language is a Central Sudanic language spoken by the Mangbetu people of northeastern Democratic Republic of the Congo.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754ac9dc8190965197024594742b |
completed | April 18, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007daef18481908c3628a3466300ce |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:17 a.m.