Triple
T17929462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Carbide Corporation |
E448289
|
entity |
| Predicate | hasLiabilityIssues |
P4511
|
FINISHED |
| Object | Bhopal disaster claims |
—
|
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: Bhopal disaster claims | Statement: [Union Carbide Corporation, hasLiabilityIssues, Bhopal disaster claims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiabilityIssues Context triple: [Union Carbide Corporation, hasLiabilityIssues, Bhopal disaster claims]
-
A.
hasLegalIssue
chosen
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
B.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
C.
liabilityType
Indicates the specific category or nature of liability associated with an entity, obligation, or financial exposure.
-
D.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
E.
hasBackIssues
Indicates that an entity experiences or possesses problems, conditions, or complications related to its back.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a5511a408190973cf5fa1f286a26 |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.