Triple
T25911270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nachtigal Hydropower Project |
E652901
|
entity |
| Predicate | PPAWith |
P122055
|
FINISHED |
| Object | ENEO Cameroon |
—
|
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: ENEO Cameroon | Statement: [Nachtigal Hydropower Project, PPAWith, ENEO Cameroon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PPAWith Context triple: [Nachtigal Hydropower Project, PPAWith, ENEO Cameroon]
-
A.
PPAOfftaker
chosen
Indicates a relationship where one party agrees to purchase electricity or energy output under a Power Purchase Agreement from another party.
-
B.
hasPP
Indicates that an entity is associated with a particular prepositional phrase (PP) that modifies or relates to it in a syntactic or semantic structure.
-
C.
ppi
Indicates a protein–protein interaction exists between the two entities.
-
D.
PPPWith
Indicates that one entity is associated or involved together with another entity in a shared context, condition, or configuration.
-
E.
PPAType
Indicates a specific type or category of a PPA (Power Purchase Agreement) relationship between parties.
- 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_69f603c5bd048190a8505dd3cef779ed |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:28 a.m.