Triple
T22618088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akosombo |
E558199
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Akan |
—
|
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: Akan | Statement: [Akosombo, languageSpoken, Akan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Akan Context triple: [Akosombo, languageSpoken, Akan]
-
A.
Akan
chosen
Akan is a major Central Tano language spoken primarily in Ghana and parts of Côte d’Ivoire, serving as a key lingua franca and cultural language for the Akan people.
-
B.
Akan
Akan is a region in eastern Hokkaido, Japan, renowned for its volcanic landscapes, crater lakes, and rich Ainu cultural heritage.
-
C.
Akena
Akena is a Ugandan surname notably borne by politician Jimmy Akena, associated with the country’s contemporary political landscape.
-
D.
Osanobua
Osanobua is the supreme creator god and central deity in the traditional religion and cosmology of the Edo people of Nigeria.
-
E.
Ayan
Ayan is a remote settlement in Russia’s Khabarovsk Krai, known as a small port village on the Sea of Okhotsk.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167ef7a148190870334af9c8b79a4 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 2:59 p.m.