Triple
T24577490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korovin Volcano |
E608152
|
entity |
| Predicate | hasSeismicMonitoring |
P154737
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Korovin Volcano, hasSeismicMonitoring, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeismicMonitoring Context triple: [Korovin Volcano, hasSeismicMonitoring, yes]
-
A.
seismicMonitoring
chosen
Indicates the ongoing observation and measurement of seismic activity or ground motion to detect, record, and analyze earthquakes or related geophysical events.
-
B.
hasVolcanicMonitoring
Indicates that an entity is subject to, or equipped with, systems or activities for monitoring volcanic activity.
-
C.
hasSeismicBehavior
Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
-
D.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
E.
seismologicalOrganization
Indicates that an entity is a seismological organization, i.e., an institution responsible for studying, monitoring, or reporting seismic activity.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a97be2ac8190aecf5e54a37e266a |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.