Triple
T26302208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Hierro volcano |
E661585
|
entity |
| Predicate | hasMonitoringNetwork |
P80146
|
FINISHED |
| Object | seismic stations |
—
|
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 stations | Statement: [El Hierro volcano, hasMonitoringNetwork, seismic stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonitoringNetwork Context triple: [El Hierro volcano, hasMonitoringNetwork, seismic stations]
-
A.
hasSatelliteMonitoring
Indicates that an entity is being observed or tracked using satellite-based monitoring systems.
-
B.
isMonitored
Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
-
C.
canBeMonitoredWith
chosen
Indicates that one entity is suitable or able to be observed, tracked, or supervised using another specified entity or method.
-
D.
isMonitoredIn
Indicates that an entity is being observed, tracked, or supervised within a particular context, system, or environment.
-
E.
hasTrafficMonitoring
Indicates that an entity is equipped with or associated with a system or capability for observing, measuring, or analyzing traffic conditions or flows.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 26, 2026, 10:16 p.m.