Triple
T25911229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edea Dam |
E652900
|
entity |
| Predicate | majorCityGridServed |
P112697
|
FINISHED |
| Object | Douala |
—
|
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: Douala | Statement: [Edea Dam, majorCityGridServed, Douala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCityGridServed Context triple: [Edea Dam, majorCityGridServed, Douala]
-
A.
modernCityServed
Indicates that a modern city receives services, support, or functions (such as transportation, utilities, or administration) from a specified provider or infrastructure.
-
B.
majorIntermediateCityServed
chosen
Indicates that a major intermediate city lies along a route or corridor and is served by the associated service or infrastructure.
-
C.
alternativeCityServed
Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
-
D.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
-
E.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
- F. None of above.
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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 22, 2026, 8:28 a.m.