Triple
T33858938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irosin |
E867868
|
entity |
| Predicate | locatedInVolcanicCaldera |
P50363
|
FINISHED |
| Object | Irosin Caldera |
E2072770
|
NE 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: Irosin Caldera | Statement: [Irosin, locatedInVolcanicCaldera, Irosin Caldera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInVolcanicCaldera Context triple: [Irosin, locatedInVolcanicCaldera, Irosin Caldera]
-
A.
locatedInCalderaOf
chosen
Indicates that one entity is situated within the caldera (the large volcanic crater) of another entity.
-
B.
containsVolcanicRegion
Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
-
C.
isPartOfVolcanicSystem
Indicates that one entity belongs to, or is a component within, a larger volcanic system or complex.
-
D.
nearVolcano
Indicates that one entity is located in close proximity to a volcano.
-
E.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
- F. None of above.
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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3689c39d7481908a5d5fd908326294 |
completed | June 20, 2026, 12:38 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.