Triple
T7163094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendeleev Volcano |
E166994
|
entity |
| Predicate | hasThermalManifestations |
P39404
|
FINISHED |
| Object | steam vents |
—
|
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: steam vents | Statement: [Mendeleev Volcano, hasThermalManifestations, steam vents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThermalManifestations Context triple: [Mendeleev Volcano, hasThermalManifestations, steam vents]
-
A.
hasThermalActivity
chosen
Indicates that an entity exhibits or is associated with heat-related phenomena such as heating, cooling, or temperature change.
-
B.
manifestationsInclude
Indicates that one entity’s manifestations or concrete expressions contain or encompass those of another entity.
-
C.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
D.
symptomAssociatedWithInfection
Indicates that a particular symptom is linked to, or commonly occurs as a result of, a specific infection.
-
E.
usesThermals
Indicates that one entity relies on rising warm air currents (thermals) as a means to gain lift, move, or maintain altitude.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e82feee481908fa180ea8c9924fa |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.