Triple
T24841575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canary hotspot |
E621626
|
entity |
| Predicate | heatSourceFor |
P38384
|
FINISHED |
| Object | partial melting of upper mantle beneath Canary Islands |
—
|
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: partial melting of upper mantle beneath Canary Islands | Statement: [Canary hotspot, heatSourceFor, partial melting of upper mantle beneath Canary Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heatSourceFor Context triple: [Canary hotspot, heatSourceFor, partial melting of upper mantle beneath Canary Islands]
-
A.
heatSource
chosen
Indicates that one entity serves as a source of heat or heating for another entity.
-
B.
heatFlow
Indicates the transfer of thermal energy from one entity or region to another due to a temperature difference.
-
C.
hasCoolingSource
Indicates that one entity provides or serves as a cooling source for another entity.
-
D.
losesHeatTo
Indicates that one entity transfers thermal energy to another, resulting in a decrease in the first entity’s heat.
-
E.
thermalStateFor
Indicates a relationship where one entity specifies or defines the thermal condition or temperature-related state of 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:18 a.m.