Triple
T16285221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhopal disaster |
E395372
|
entity |
| Predicate | chemicalInvolved |
P53893
|
FINISHED |
| Object | methyl isocyanate |
—
|
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: methyl isocyanate | Statement: [Bhopal disaster, chemicalInvolved, methyl isocyanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chemicalInvolved Context triple: [Bhopal disaster, chemicalInvolved, methyl isocyanate]
-
A.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient of another entity.
-
B.
keyChemicalDiscussed
chosen
Indicates that a particular chemical substance is a central topic of discussion in a given context or communication.
-
C.
usesChemistry
Indicates that one entity applies or relies on chemistry, chemical methods, or chemical principles in relation to another entity or context.
-
D.
commonChemistry
Indicates that two entities share similar or related chemical properties, composition, or behavior.
-
E.
chemicallyRelatedTo
Indicates a relationship where two entities are connected through a chemical association, such as sharing structural features, participating in related reactions, or being derivable from one another chemically.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24913a55081909a9a5a7a7f4806cc |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.