Triple
T16285261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhopal disaster |
E395372
|
entity |
| Predicate | longTermIssue |
P122526
|
FINISHED |
| Object | incomplete site cleanup |
—
|
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: incomplete site cleanup | Statement: [Bhopal disaster, longTermIssue, incomplete site cleanup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longTermIssue Context triple: [Bhopal disaster, longTermIssue, incomplete site cleanup]
-
A.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
B.
longLived
Indicates that an entity has a lifespan or duration of existence significantly longer than what is typical or expected in its context.
-
C.
laterOperationalIssue
Indicates that an operational issue occurred at some point after a referenced time, event, or condition.
-
D.
durationOfAffliction
Indicates the length of time that an affliction or condition persists for an entity.
-
E.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.