Triple
T9555167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcanoes of Kamchatka |
E230521
|
entity |
| Predicate | mainThreats |
P23662
|
FINISHED |
| Object | tourism pressure |
—
|
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: tourism pressure | Statement: [Volcanoes of Kamchatka, mainThreats, tourism pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainThreats Context triple: [Volcanoes of Kamchatka, mainThreats, tourism pressure]
-
A.
primaryThreat
chosen
Indicates that one entity is the main or most significant source of danger, harm, or risk to another entity.
-
B.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
-
C.
threatsManaged
Indicates that one entity takes responsibility for identifying, controlling, or mitigating risks or dangers affecting another entity or system.
-
D.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
E.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd992412148190b092bd9918764d5f |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.