Triple
T36878752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bromo-Seltzer |
E911414
|
entity |
| Predicate | regulatoryChangeReason |
P5019
|
FINISHED |
| Object | safety concerns about bromide toxicity |
—
|
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: safety concerns about bromide toxicity | Statement: [Bromo-Seltzer, regulatoryChangeReason, safety concerns about bromide toxicity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryChangeReason Context triple: [Bromo-Seltzer, regulatoryChangeReason, safety concerns about bromide toxicity]
-
A.
regulationReason
Indicates the reason or justification for which a regulation is established, applied, or enforced in relation to an entity or activity.
-
B.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
C.
typeOfChangeRegulated
Indicates that one entity specifies or controls the kind of change or modification that is allowed or governed in another entity or process.
-
D.
changeReason
chosen
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
regulationChangeComparedToPrevious
Indicates a change in a regulation relative to its immediately preceding version or state.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 3, 2026, 4:13 p.m.