Triple
T16665336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telica |
E404967
|
entity |
| Predicate | hasThermalFeature |
P120154
|
FINISHED |
| Object | hot fumaroles |
—
|
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: hot fumaroles | Statement: [Telica, hasThermalFeature, hot fumaroles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThermalFeature Context triple: [Telica, hasThermalFeature, hot fumaroles]
-
A.
hasThermalCharacteristic
Indicates that an entity possesses a specific thermal property or behavior, such as conductivity, capacity, or response to temperature.
-
B.
hasThermalResource
chosen
Indicates that an entity possesses, provides, or is associated with a source of thermal energy or heat-related capability.
-
C.
hasThermalActivity
Indicates that an entity exhibits or is associated with heat-related phenomena such as heating, cooling, or temperature change.
-
D.
usesThermals
Indicates that one entity relies on rising warm air currents (thermals) as a means to gain lift, move, or maintain altitude.
-
E.
hasThermalEstablishment
Indicates that one entity is responsible for creating, setting, or defining the thermal conditions or temperature 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9be0688190afda306cde934c68 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.