Triple
T30131544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Forest |
E765857
|
entity |
| Predicate | hazardClassification |
P155938
|
FINISHED |
| Object | high-radiation hotspot within exclusion zone |
—
|
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: high-radiation hotspot within exclusion zone | Statement: [Red Forest, hazardClassification, high-radiation hotspot within exclusion zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardClassification Context triple: [Red Forest, hazardClassification, high-radiation hotspot within exclusion zone]
-
A.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
B.
hazardLevelSystem
chosen
Indicates a system’s assigned degree of risk or danger within a defined hazard classification framework.
-
C.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
D.
hasHazardCharacteristic
Indicates that an entity possesses a specific hazardous property, condition, or risk-related characteristic.
-
E.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e48471c8190b3b488c00f5d0b37 |
completed | May 2, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:15 p.m.