Triple
T27916459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooking at El Diablo restaurant |
E706087
|
entity |
| Predicate | usesHeatSource |
P38384
|
FINISHED |
| Object | natural volcanic 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: natural volcanic heat | Statement: [Cooking at El Diablo restaurant, usesHeatSource, natural volcanic heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHeatSource Context triple: [Cooking at El Diablo restaurant, usesHeatSource, natural volcanic heat]
-
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.
losesHeatTo
Indicates that one entity transfers thermal energy to another, resulting in a decrease in the first entity’s heat.
-
D.
usesThermals
Indicates that one entity relies on rising warm air currents (thermals) as a means to gain lift, move, or maintain altitude.
-
E.
hasThermalResource
Indicates that an entity possesses, provides, or is associated with a source of thermal energy or heat-related capability.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:54 p.m.