Triple
T34770073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corexit EC9527A |
E1002338
|
entity |
| Predicate | potentialEffect |
P39645
|
FINISHED |
| Object | eye irritation |
—
|
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: eye irritation | Statement: [Corexit EC9527A, potentialEffect, eye irritation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potentialEffect Context triple: [Corexit EC9527A, potentialEffect, eye irritation]
-
A.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
-
B.
possibleSideEffect
chosen
Indicates that one entity may occur as a side effect or unintended consequence of another entity or action.
-
C.
conditionalEffect
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
-
D.
primaryEffect
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
E.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.