Triple
T24216689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geysir geothermal area |
E601323
|
entity |
| Predicate | primaryHeatSource |
P38384
|
FINISHED |
| Object | magma intrusions |
—
|
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: magma intrusions | Statement: [Geysir geothermal area, primaryHeatSource, magma intrusions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHeatSource Context triple: [Geysir geothermal area, primaryHeatSource, magma intrusions]
-
A.
heatSource
chosen
Indicates that one entity serves as a source of heat or heating for another entity.
-
B.
hasCoolingSource
Indicates that one entity provides or serves as a cooling source for another entity.
-
C.
hasHydrothermalActivity
Indicates that a location or geological feature exhibits hydrothermal activity, such as the circulation of heated water or fluids associated with geothermal processes.
-
D.
hasLowerSurfaceTemperatureThan
Indicates that the surface temperature of one entity is lower than the surface temperature of another entity.
-
E.
primaryHeatingFuel
Indicates the type of fuel or energy source that is mainly used for heating a building or space.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28208d87081909b32c84328b8f3ba |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:58 p.m.