Triple
T17122573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dobu |
E415504
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Dobu language |
E439607
|
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: Dobu language | Statement: [Dobu, hasLanguage, Dobu language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dobu language Context triple: [Dobu, hasLanguage, Dobu language]
-
A.
Dobu language
chosen
Dobu language is an Austronesian language of the Papuan Tip region of Papua New Guinea, traditionally spoken by the Dobu people and used as a local lingua franca.
-
B.
Dobbi language
The Dobbi language is an Ethiopian Semitic language spoken by the Gurage people as part of the broader Gurage language group.
-
C.
Dibo language
The Dibo language is a Nupoid language spoken by the Dibo people of central Nigeria.
-
D.
Logba language
The Logba language is a Niger-Congo language spoken by the Logba people of southeastern Ghana.
-
E.
Uduk language
The Uduk language is a Nilo-Saharan language spoken primarily by the Uduk people of eastern Sudan and western Ethiopia.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e80ac2cc819084fab829917c950a |
completed | April 18, 2026, 8:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a013a1062fc8190b1c4e97f42cf3faa |
completed | May 11, 2026, 2:08 a.m. |
Created at: April 10, 2026, 5:36 a.m.