Triple
T25811838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Slamet |
E650132
|
entity |
| Predicate | hasSummitCraters |
P15606
|
FINISHED |
| Object | multiple craters |
—
|
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: multiple craters | Statement: [Mount Slamet, hasSummitCraters, multiple craters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitCraters Context triple: [Mount Slamet, hasSummitCraters, multiple craters]
-
A.
hasSummitCaldera
Indicates that an entity (typically a volcano) possesses a caldera located at or near its summit.
-
B.
summitCrater
chosen
Indicates the relationship where a crater is located at or forms the summit of a volcanic or mountainous feature.
-
C.
hasMultipleSummits
Indicates that an entity (such as a mountain or peak) consists of more than one distinct summit or high point.
-
D.
hasSummitFacility
Indicates that one entity possesses or provides a facility or infrastructure located at the summit of another entity (such as a mountain, hill, or peak).
-
E.
summitCraterType
Indicates the specific type or classification of a volcano’s summit crater associated with an entity.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 22, 2026, 7:10 a.m.