Triple
T23371993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Матуа |
E593498
|
entity |
| Predicate | имеетОпасность |
P16293
|
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.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
B.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
C.
имеетКодОпасностиДляАвиации
Indicates that an entity is assigned a specific aviation hazard code defining its level or type of danger to air traffic or aviation operations.
-
D.
hasNotableHazard
chosen
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.