Triple
T9541898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plotosidae |
E230176
|
entity |
| Predicate | venomEffectOnHumans |
P17207
|
FINISHED |
| Object | painful sting |
—
|
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: painful sting | Statement: [Plotosidae, venomEffectOnHumans, painful sting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venomEffectOnHumans Context triple: [Plotosidae, venomEffectOnHumans, painful sting]
-
A.
venomAllergenicToHumans
Indicates that a particular venom causes allergic reactions or hypersensitivity responses in humans.
-
B.
venomous
Indicates that an organism possesses venom and can inject or deliver it to another organism, typically as a means of defense or predation.
-
C.
venomFunction
chosen
Indicates the specific biological role or effect that a venom has when acting on a target.
-
D.
toxinEffect
Indicates the harmful impact or physiological response caused by a toxin on a target entity.
-
E.
pathogenicityToHumans
Indicates that an entity has the capacity to cause disease or harmful health effects in humans.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e82bb08190aed3ed0627923d22 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.