Triple
T8342076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timanfaya National Park |
E195940
|
entity |
| Predicate | hasHotspots |
P48172
|
FINISHED |
| Object | subsurface geothermal 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: subsurface geothermal heat | Statement: [Timanfaya National Park, hasHotspots, subsurface geothermal heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHotspots Context triple: [Timanfaya National Park, hasHotspots, subsurface geothermal heat]
-
A.
hotspot
chosen
Indicates that a location or entity is a focal point of intense activity, interest, or occurrence relative to others.
-
B.
hasHotSpring
Indicates that one entity possesses, contains, or is associated with a hot spring.
-
C.
hotspotType
Indicates the specific category or kind of hotspot associated with an entity or location.
-
D.
isHotspotTrackOf
Indicates that one entity is a hotspot track that corresponds to, or is derived from, another entity.
-
E.
hasBrightSpots
Indicates that an entity possesses one or more areas or points that are noticeably brighter than their surroundings.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fe9efec81908e0c9ded3963bac5 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:58 p.m.