Triple
T13523630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Klabat |
E322963
|
entity |
| Predicate | craterLakeLocation |
P110678
|
FINISHED |
| Object | summit crater |
—
|
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: summit crater | Statement: [Mount Klabat, craterLakeLocation, summit crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craterLakeLocation Context triple: [Mount Klabat, craterLakeLocation, summit crater]
-
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.
hasIslandInCraterLake
Indicates that a crater lake contains an island located within it.
-
D.
craterLakeNotability
Indicates that an entity is notable or significant specifically for having or being associated with a crater lake.
-
E.
hasCraterLakeName
Indicates that an entity has, is associated with, or is identified by the name of a crater lake.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa535cc81908d0018fef81a2848 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.