Triple
T34113605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crackling Lake |
E874905
|
entity |
| Predicate | geothermalEnergySource |
P38384
|
FINISHED |
| Object | Yellowstone hotspot |
—
|
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: Yellowstone hotspot | Statement: [Crackling Lake, geothermalEnergySource, Yellowstone hotspot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geothermalEnergySource Context triple: [Crackling Lake, geothermalEnergySource, Yellowstone hotspot]
-
A.
hasGeothermalPotential
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
-
B.
heatSource
chosen
Indicates that one entity serves as a source of heat or heating for another entity.
-
C.
isGeothermalFieldType
Indicates that one entity is classified as a specific type or category of geothermal field in relation to another entity.
-
D.
hasGeothermalField
Indicates that an entity possesses, contains, or is associated with a geothermal field.
-
E.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb777d88190a2aed1a880d4b613 |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.