Triple
T25911228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edea Dam |
E652900
|
entity |
| Predicate | countryCapitalGridServed |
P179184
|
FINISHED |
| Object | Yaoundé |
—
|
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: Yaoundé | Statement: [Edea Dam, countryCapitalGridServed, Yaoundé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCapitalGridServed Context triple: [Edea Dam, countryCapitalGridServed, Yaoundé]
-
A.
connectsCapitalOf
Indicates a relationship where one entity serves as the capital city of another entity, linking the capital to the political or administrative unit it represents.
-
B.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
C.
countryCapitalLocatedOn
Indicates that the capital city of a country is situated on or directly adjacent to a specified geographic feature (such as a river, coast, or lake).
-
D.
destinationCapitalOf
Indicates that a location serves as the capital city of the specified destination or region.
-
E.
countryCapitalOfSeat
Indicates that a country serves as the capital location or official seat of a specified entity, such as an organization or institution.
- F. None of above. chosen
Provenance (4 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 22, 2026, 8:28 a.m.