Triple
T25826043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Carbide India Limited |
E650531
|
entity |
| Predicate | operatedFacilityResponsibleFor |
P4904
|
FINISHED |
| Object | Bhopal disaster |
—
|
NE NERFINISHED |
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: Bhopal disaster | Statement: [Union Carbide India Limited, operatedFacilityResponsibleFor, Bhopal disaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedFacilityResponsibleFor Context triple: [Union Carbide India Limited, operatedFacilityResponsibleFor, Bhopal disaster]
-
A.
facilityOperatedBy
Indicates that a facility is managed, run, or controlled by a specified agent or organization.
-
B.
operatesFacility
chosen
Indicates that an entity is responsible for running, managing, or controlling the operations of a particular facility.
-
C.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
D.
operatesFacilitiesType
Indicates that an entity runs or manages facilities of a specified type.
-
E.
isFacilityOf
Indicates that a facility (such as a building, site, or infrastructure) belongs to, is operated by, or is associated with a particular organization, entity, or system.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 22, 2026, 7:36 a.m.