Triple
T28818752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delamar, Nevada |
E727701
|
entity |
| Predicate | healthHazard |
P1950
|
FINISHED |
| Object | silica dust from ore crushing |
—
|
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: silica dust from ore crushing | Statement: [Delamar, Nevada, healthHazard, silica dust from ore crushing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthHazard Context triple: [Delamar, Nevada, healthHazard, silica dust from ore crushing]
-
A.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
B.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
D.
hazardEncountered
Indicates that an entity has come into contact with or been exposed to a potentially dangerous or harmful condition, object, or situation.
-
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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f54d4c819098307e82a2a6e892 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:33 a.m.