Triple
T34770088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corexit EC9527A |
E1002338
|
entity |
| Predicate | hasCASStatus |
P116090
|
FINISHED |
| Object | mixture with proprietary composition |
—
|
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: mixture with proprietary composition | Statement: [Corexit EC9527A, hasCASStatus, mixture with proprietary composition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCASStatus Context triple: [Corexit EC9527A, hasCASStatus, mixture with proprietary composition]
-
A.
hasCAS
Indicates that an entity is associated with a specific Chemical Abstracts Service (CAS) registry number identifying it as a distinct chemical substance.
-
B.
hasCabinetStatus
Indicates that an entity holds a specific status or role within a cabinet-level governing body.
-
C.
hasFacilityStatusFor
Indicates that an entity has a particular operational or condition status assigned to a specific facility.
-
D.
hasStatusBasedOn
chosen
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
E.
hasIMAStatus
Indicates that an entity holds a specific IMA (Integrity Measurement Architecture) status or condition.
- 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_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.