Triple
T7409734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canary hotspot volcanic system |
E170969
|
entity |
| Predicate | heatSourceType |
P38384
|
FINISHED |
| Object | deep mantle plume |
—
|
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: deep mantle plume | Statement: [Canary hotspot volcanic system, heatSourceType, deep mantle plume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heatSourceType Context triple: [Canary hotspot volcanic system, heatSourceType, deep mantle plume]
-
A.
heatSource
chosen
Indicates that one entity serves as a source of heat or heating for another entity.
-
B.
heatingMethod
Indicates the method or technique used to apply heat to something, such as for cooking, warming, or processing.
-
C.
hasCoolingSource
Indicates that one entity provides or serves as a cooling source for another entity.
-
D.
heatFlow
Indicates the transfer of thermal energy from one entity or region to another due to a temperature difference.
-
E.
boilerType
Indicates the specific kind or category of boiler associated with an entity, such as its design, fuel source, or operating characteristics.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f29d77848190a6170eb25483224f |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.