Triple
T2361329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetraodontiformes |
E47277
|
entity |
| Predicate | toxin |
P8036
|
FINISHED |
| Object | tetrodotoxin in many pufferfish |
—
|
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: tetrodotoxin in many pufferfish | Statement: [Tetraodontiformes, toxin, tetrodotoxin in many pufferfish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toxin Context triple: [Tetraodontiformes, toxin, tetrodotoxin in many pufferfish]
-
A.
toxinType
chosen
Indicates the specific kind or category of toxin associated with an entity.
-
B.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
-
C.
venomous
Indicates that an organism possesses venom and can inject or deliver it to another organism, typically as a means of defense or predation.
-
D.
virulence
Indicates the degree to which a pathogen or harmful agent is capable of causing damage, disease, or severe effects in its host.
-
E.
notableSubstanceReleased
Indicates that an entity has released or emitted a particular notable substance.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc723c66481908a9b94991f651b3b |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.