Triple
T16288793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obetia radula |
E395461
|
entity |
| Predicate | hasToxinEffect |
P54346
|
FINISHED |
| Object | causes skin irritation on contact |
—
|
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: causes skin irritation on contact | Statement: [Obetia radula, hasToxinEffect, causes skin irritation on contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasToxinEffect Context triple: [Obetia radula, hasToxinEffect, causes skin irritation on contact]
-
A.
toxinEffect
chosen
Indicates the harmful impact or physiological response caused by a toxin on a target entity.
-
B.
poisonUsed
Indicates that one entity employed poison as a means to harm, kill, or incapacitate another entity.
-
C.
toxinType
Indicates the specific kind or category of toxin associated with an entity.
-
D.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
-
E.
toxinProduced
Indicates that one entity generates or secretes a substance that is toxic or harmful to another entity or its environment.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e249165af881908ce44c4517c93c12 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.