Triple
T26296451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tvashtar Paterae |
E661431
|
entity |
| Predicate | eruptionTemperature |
P87663
|
FINISHED |
| Object | very high-temperature silicate volcanism |
—
|
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: very high-temperature silicate volcanism | Statement: [Tvashtar Paterae, eruptionTemperature, very high-temperature silicate volcanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionTemperature Context triple: [Tvashtar Paterae, eruptionTemperature, very high-temperature silicate volcanism]
-
A.
lavaTemperature
chosen
Indicates the temperature value associated with lava in a given context or state.
-
B.
eruptionHeight
Indicates the vertical distance or altitude reached by an eruption from its source.
-
C.
eruptionPotential
Indicates the likelihood or capacity of something (typically a volcano or similar system) to erupt under given conditions.
-
D.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
-
E.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eaea1d08190b93b85590b8c9781 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:12 p.m.