Triple
T9269491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guruntum |
E222786
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Guruntum-Mbaaru |
E222786
|
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: Guruntum-Mbaaru | Statement: [Guruntum, hasAlternativeName, Guruntum-Mbaaru]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guruntum-Mbaaru Context triple: [Guruntum, hasAlternativeName, Guruntum-Mbaaru]
-
A.
Guruntum
chosen
Guruntum is a West Chadic language spoken by a relatively small ethnic community in Nigeria.
-
B.
Gashua
Gashua is a town in northeastern Nigeria that serves as an important commercial and administrative center in Yobe State.
-
C.
Mandura Gumuz
Mandura Gumuz is a Gumuz language spoken by the Gumuz people of western Ethiopia.
-
D.
Ngamo
Ngamo is a West Chadic language spoken primarily in northeastern Nigeria by the Ngamo people.
-
E.
Barka Kunama
Barka Kunama is a dialect of the Kunama language spoken by Kunama communities, primarily in parts of Eritrea and neighboring regions.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd074ef7408190b213c09491918132 |
completed | April 1, 2026, 11:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09c2239a08190b954c8c57ced8fd2 |
completed | April 4, 2026, 5:05 a.m. |
Created at: March 30, 2026, 7:33 p.m.