Triple
T32858179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hutchinson Salt Member deposits |
E840435
|
entity |
| Predicate | hazardAssociation |
P138266
|
FINISHED |
| Object | risk of subsidence where salt is dissolved |
—
|
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: risk of subsidence where salt is dissolved | Statement: [Hutchinson Salt Member deposits, hazardAssociation, risk of subsidence where salt is dissolved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardAssociation Context triple: [Hutchinson Salt Member deposits, hazardAssociation, risk of subsidence where salt is dissolved]
-
A.
hasHazardRelation
chosen
Indicates a relationship where one entity poses, contributes to, or is associated with a potential hazard or risk affecting another entity.
-
B.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
D.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
E.
hazardEvent
Indicates an occurrence of a dangerous or harmful event that poses a risk or threat within a given context.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ceb2b81c81909c1a186305a9d597 |
completed | May 3, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.