Triple
T11729468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lewisite |
E278861
|
entity |
| Predicate | hasToxicity |
P54183
|
FINISHED |
| Object | highly toxic |
—
|
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: highly toxic | Statement: [lewisite, hasToxicity, highly toxic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasToxicity Context triple: [lewisite, hasToxicity, highly toxic]
-
A.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
-
B.
notableToxicity
chosen
Indicates that an entity is recognized for having a significant level or history of toxicity, harm, or detrimental effects in its context or interactions.
-
C.
toxinType
Indicates the specific kind or category of toxin associated with an entity.
-
D.
isNonToxic
Indicates that something does not contain harmful or poisonous substances and is safe for use or exposure under normal conditions.
-
E.
toxicPart
Indicates that one entity is a component or portion of another that is harmful, poisonous, or otherwise toxic.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.