Triple
T17460262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toba Caldera |
E425132
|
entity |
| Predicate | calderaOrientation |
P127545
|
FINISHED |
| Object | northwest–southeast |
—
|
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: northwest–southeast | Statement: [Toba Caldera, calderaOrientation, northwest–southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calderaOrientation Context triple: [Toba Caldera, calderaOrientation, northwest–southeast]
-
A.
calderaDepth
Indicates the vertical distance from a caldera’s rim down to its lowest interior point.
-
B.
locatedInCalderaOf
Indicates that one entity is situated within the caldera (the large volcanic crater) of another entity.
-
C.
diameterOfCaldera
Indicates the measured width across a caldera from one rim edge to the opposite rim edge.
-
D.
summitCraterOrientation
Indicates the directional alignment or facing of a volcano’s summit crater relative to a reference frame (e.g., cardinal directions or slope aspect).
-
E.
typeOfVolcanicFeature
Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a3031c8190ab1dd0d41b002dd2 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.