Triple
T37295801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bondo District |
E925797
|
entity |
| Predicate | languageMajoritySpoken |
P11430
|
FINISHED |
| Object | Dholuo |
—
|
NE NERFINISHED |
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: Dholuo | Statement: [Bondo District, languageMajoritySpoken, Dholuo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageMajoritySpoken Context triple: [Bondo District, languageMajoritySpoken, Dholuo]
-
A.
majorityLanguageOf
chosen
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
B.
languageFamilyDominant
Indicates that one language family holds a primary or prevailing status over others within a given context (such as a region, population, or system).
-
C.
nationalLanguageSpoken
Indicates that a particular language is officially recognized and commonly used as a national language within a given country or region.
-
D.
shareMajorLanguage
Indicates that the entities have at least one primary or major language in common.
-
E.
oneOfMostSpokenLanguages
Indicates that a language is among the most widely spoken languages within a given population or context.
- F. None of above.
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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a017e7bdfe481909cb4d5bdede6035e |
completed | May 11, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_6a017defee108190bdf5f98dc415b250 |
completed | May 11, 2026, 6:57 a.m. |
Created at: May 3, 2026, 4:16 p.m.