Triple
T22618069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akosombo |
E558199
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Akosombo Dam |
—
|
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: Akosombo Dam | Statement: [Akosombo, near, Akosombo Dam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Akosombo Dam Context triple: [Akosombo, near, Akosombo Dam]
-
A.
Akosombo Dam
chosen
Akosombo Dam is a major hydroelectric dam in Ghana that created Lake Volta and supplies a significant portion of the country’s electricity.
-
B.
Gambo Dam
Gambo Dam is a hydroelectric and flood-control dam located on the Presumpscot River in Maine.
-
C.
Afobaka Dam
Afobaka Dam is a major hydroelectric dam in Suriname that created the Brokopondo Reservoir and supplies much of the country’s electricity.
-
D.
Roseires Dam
Roseires Dam is a major hydroelectric and irrigation dam on the Blue Nile in Sudan, crucial for water storage, power generation, and flood control in the region.
-
E.
Nam River Dam
Nam River Dam is a major multipurpose dam in South Korea used primarily for flood control, water supply, and hydroelectric power generation on the Nam River.
- 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.