Triple
T22854551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-326 |
E566443
|
entity |
| Predicate | associatedHazardClass |
P1950
|
FINISHED |
| Object | nuclear facility with radiological hazards |
—
|
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: nuclear facility with radiological hazards | Statement: [X-326, associatedHazardClass, nuclear facility with radiological hazards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedHazardClass Context triple: [X-326, associatedHazardClass, nuclear facility with radiological hazards]
-
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.
hasHazardRelation
Indicates a relationship where one entity poses, contributes to, or is associated with a potential hazard or risk affecting another entity.
-
D.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
E.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebb4ea48190b4b865e316f6a75f |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.