Triple
T10596295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutnovskaya geothermal power plant |
E250120
|
entity |
| Predicate | usesHeatFrom |
P38384
|
FINISHED |
| Object | Earth’s internal heat |
—
|
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: Earth’s internal heat | Statement: [Mutnovskaya geothermal power plant, usesHeatFrom, Earth’s internal heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHeatFrom Context triple: [Mutnovskaya geothermal power plant, usesHeatFrom, Earth’s internal heat]
-
A.
usesThermals
Indicates that one entity relies on rising warm air currents (thermals) as a means to gain lift, move, or maintain altitude.
-
B.
heatSource
chosen
Indicates that one entity serves as a source of heat or heating for another entity.
-
C.
hasHeating
Indicates that an entity is equipped with or provides a heating system or heating capability.
-
D.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
E.
emitsMoreEnergyThanItReceives
Indicates that the subject releases a greater amount of energy than it takes in from its surroundings or inputs.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278dacc4819089b759744f100e5f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.