Triple
T12989555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biu |
E321866
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Bura language |
E788834
|
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: Bura language | Statement: [Biu, hasLanguage, Bura language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bura language Context triple: [Biu, hasLanguage, Bura language]
-
A.
Bura language
chosen
Bura language is a Chadic language spoken primarily in northeastern Nigeria by the Bura people.
-
B.
Buru languages
Buru languages are a small group of closely related Austronesian languages spoken primarily on Buru Island in Indonesia’s Maluku region.
-
C.
Bura-Pabir language
The Bura-Pabir language is a Chadic language spoken primarily in northeastern Nigeria by the Bura and Pabir ethnic groups.
-
D.
Bafia language
The Bafia language is a Bantu language spoken primarily by the Bafia people in central Cameroon.
-
E.
Bunak language
The Bunak language is a Papuan language spoken primarily in the central region of Timor, straddling the border between Indonesia and Timor-Leste.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e75b9f88190a54372c2a1223a4e |
completed | April 10, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8f942588190b69a3067d5145182 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:43 p.m.