Triple
T17254037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craters of the Moon geothermal area |
E418832
|
entity |
| Predicate | hasClimateImpact |
P3009
|
FINISHED |
| Object | steam emissions |
—
|
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: steam emissions | Statement: [Craters of the Moon geothermal area, hasClimateImpact, steam emissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimateImpact Context triple: [Craters of the Moon geothermal area, hasClimateImpact, steam emissions]
-
A.
hasClimateInfluence
chosen
Indicates that one entity affects or contributes to the climate characteristics or climate-related conditions of another entity.
-
B.
hasEnvironmentalImpactOn
Indicates that one entity affects or alters the environmental conditions, quality, or ecological state of another entity.
-
C.
hasEnvironmentalImpactType
Indicates that something affects the environment in a specific way categorized by a particular type of impact.
-
D.
hasClimate
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
E.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6b2b1c8190b446ce648ecaad80 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.