Triple
T2476132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Licancabur |
E55092
|
entity |
| Predicate | craterLakeNotability |
P39707
|
FINISHED |
| Object | one of the highest lakes in the world |
—
|
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: one of the highest lakes in the world | Statement: [Licancabur, craterLakeNotability, one of the highest lakes in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craterLakeNotability Context triple: [Licancabur, craterLakeNotability, one of the highest lakes in the world]
-
A.
craterLakeType
Indicates that the subject is a lake formed in or associated with a volcanic crater, specifying this particular type of lake.
-
B.
craterLakeDepth
Indicates the depth measurement of a crater lake, typically from its surface to the deepest point.
-
C.
hasCraterNamedAfter
Indicates that a crater is named in honor of a particular person, place, or entity.
-
D.
summitCrater
Indicates the relationship where a crater is located at or forms the summit of a volcanic or mountainous feature.
-
E.
notableGlacier
Indicates that the subject is a glacier recognized for its particular significance, prominence, or noteworthiness.
- F. None of above. chosen
Provenance (4 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1e45380819094b3f32a278bd457 |
completed | March 7, 2026, 7:21 a.m. |
Created at: March 6, 2026, 9:45 p.m.