Triple
T9644724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Карымский |
E233164
|
entity |
| Predicate | категорияОпасности |
P1950
|
FINISHED |
| Object | активный и потенциально опасный вулкан |
—
|
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: активный и потенциально опасный вулкан | Statement: [Карымский, категорияОпасности, активный и потенциально опасный вулкан]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: категорияОпасности Context triple: [Карымский, категорияОпасности, активный и потенциально опасный вулкан]
-
A.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
B.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
C.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
D.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
E.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7fd2308190803a196ecdc80d76 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.