Triple
T695907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medicine Lake Volcano |
E13892
|
entity |
| Predicate | hasGlacialFeature |
P8808
|
FINISHED |
| Object | paternoster lakes in caldera |
—
|
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: paternoster lakes in caldera | Statement: [Medicine Lake Volcano, hasGlacialFeature, paternoster lakes in caldera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlacialFeature Context triple: [Medicine Lake Volcano, hasGlacialFeature, paternoster lakes in caldera]
-
A.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
B.
glaciationCharacteristic
chosen
Indicates that one entity is a characteristic, feature, or property associated with the process or effects of glaciation of another entity.
-
C.
notableGlacier
Indicates that the subject is a glacier recognized for its particular significance, prominence, or noteworthiness.
-
D.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
-
E.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c5f51c8190acc4915099e4b384 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.