Triple
T7264299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ga–Dangme languages |
E159731
|
entity |
| Predicate | typologicallySimilarTo |
P8039
|
FINISHED |
| Object | Ewe language |
E53601
|
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: Ewe language | Statement: [Ga–Dangme languages, typologicallySimilarTo, Ewe language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ewe language Context triple: [Ga–Dangme languages, typologicallySimilarTo, Ewe language]
-
A.
Ewe
chosen
Ewe is a major Niger–Congo language spoken primarily in southeastern Ghana and southern Togo by the Ewe people.
-
B.
Fante language
Fante language is a major dialect of the Akan language spoken primarily by the Fante people in coastal Ghana.
-
C.
Adioukrou language
The Adioukrou language is a Kwa language spoken by the Adioukrou people of southern Côte d’Ivoire.
-
D.
Akyem Twi
Akyem Twi is a regional variety of the Akan language spoken primarily by the Akyem people in Ghana.
-
E.
Sefwi language
The Sefwi language is a Niger-Congo language spoken primarily by the Sefwi people in western Ghana.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eae50e008190a660925074077344 |
completed | March 27, 2026, 8:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d3c7754481908ff7cc0fc6419599 |
completed | March 28, 2026, 1:12 p.m. |
Created at: March 27, 2026, 2:57 p.m.