Triple
T31925369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ksudach volcano |
E815088
|
entity |
| Predicate | calderaOrigin |
P6355
|
FINISHED |
| Object | collapse after large explosive eruptions |
—
|
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: collapse after large explosive eruptions | Statement: [Ksudach volcano, calderaOrigin, collapse after large explosive eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calderaOrigin Context triple: [Ksudach volcano, calderaOrigin, collapse after large explosive eruptions]
-
A.
calderaName
Indicates that an entity is assigned the proper name of a caldera.
-
B.
calderaStructure
Indicates a structural or morphological relationship in which one geological feature forms, defines, or contributes to the caldera configuration of another.
-
C.
locatedInCalderaOf
Indicates that one entity is situated within the caldera (the large volcanic crater) of another entity.
-
D.
calderaOrientation
Indicates the directional alignment or facing of a caldera relative to a reference frame or compass directions.
-
E.
volcanicOrigin
chosen
Indicates that something originates from, is produced by, or is directly associated with volcanic activity or processes.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1fabffc81909d345f47c6692073 |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca7081881909e96a8b05ec086bb |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:03 a.m.