Triple
T38012789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN 1671 |
E948409
|
entity |
| Predicate | hasSecondaryHazard |
P142138
|
FINISHED |
| Object | corrosivity |
—
|
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: corrosivity | Statement: [UN 1671, hasSecondaryHazard, corrosivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryHazard Context triple: [UN 1671, hasSecondaryHazard, corrosivity]
-
A.
secondaryHazardType
chosen
Indicates the type or category of a hazard that occurs as a secondary or consequential effect of a primary hazard or event.
-
B.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
C.
isHazard
Indicates that something poses a potential risk, danger, or harmful condition to people, property, or the environment.
-
D.
hasHazardCharacteristic
Indicates that an entity possesses a specific hazardous property, condition, or risk-related characteristic.
-
E.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:20 p.m.