Triple
T6294378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebeko |
E141093
|
entity |
| Predicate | eruptionMonitoringMethods |
P64414
|
FINISHED |
| Object | seismic monitoring |
—
|
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: seismic monitoring | Statement: [Ebeko, eruptionMonitoringMethods, seismic monitoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionMonitoringMethods Context triple: [Ebeko, eruptionMonitoringMethods, seismic monitoring]
-
A.
hasVolcanicMonitoring
chosen
Indicates that an entity is subject to, or equipped with, systems or activities for monitoring volcanic activity.
-
B.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
C.
volcanicStatus
Indicates the current activity state or condition of a volcano, such as active, dormant, or extinct.
-
D.
eruptionFrequency
Indicates how often an eruption event occurs within a given time period.
-
E.
eruptionImpact
Indicates the effects or consequences that a volcanic eruption has on surrounding entities, environments, or systems.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06438654481908c9833c5f0d61773 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.