Triple
T35264249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kananga |
E1018461
|
entity |
| Predicate | hasEnergyContext |
P194278
|
FINISHED |
| Object | near geothermal power plants |
—
|
LITERAL FINISHED |
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: near geothermal power plants | Statement: [Kananga, hasEnergyContext, near geothermal power plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyContext Context triple: [Kananga, hasEnergyContext, near geothermal power plants]
-
A.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
B.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
C.
hasEnergyBaseStatus
Indicates that an entity has a particular fundamental or baseline energy-related status or condition.
-
D.
hasEnergyConcept
Indicates that one entity is associated with, characterized by, or defined in terms of a particular concept of energy.
-
E.
hasPowerContext
Indicates that one entity’s power, influence, or authority is defined, constrained, or interpreted within a particular situational or contextual framework.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: May 3, 2026, 4:02 p.m.