Triple
T11575140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngbandi language |
E274483
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Yakoma |
E923591
|
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: Yakoma | Statement: [Ngbandi language, hasDialect, Yakoma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yakoma Context triple: [Ngbandi language, hasDialect, Yakoma]
-
A.
Yakoma
chosen
Yakoma is a Bantu language spoken by the Yakoma people primarily in the Central African Republic.
-
B.
Shimea
Shimea is a biblical figure mentioned in the Hebrew Bible as one of King David’s brothers.
-
C.
Yokadouma
Yokadouma is a town in eastern Cameroon that serves as an important local administrative and commercial center near the country's forested border regions.
-
D.
Yato
Yato is a small village on Pukapuka Atoll in the Cook Islands, known for its traditional Polynesian community and remote Pacific island setting.
-
E.
Yamanto
Yamanto is a residential suburb in the City of Ipswich, Queensland, Australia, known for its family-friendly housing estates and growing retail and service amenities.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89048120c81908258f984711f7dd4 |
completed | April 10, 2026, 5:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e713e49f508190b9bad316d68eab42 |
completed | April 21, 2026, 6:06 a.m. |
Created at: April 8, 2026, 9:38 p.m.