Triple
T3863125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrmeciinae |
E90185
|
entity |
| Predicate | venomEffect |
P17207
|
FINISHED |
| Object | can cause severe allergic reactions in humans |
—
|
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: can cause severe allergic reactions in humans | Statement: [Myrmeciinae, venomEffect, can cause severe allergic reactions in humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venomEffect Context triple: [Myrmeciinae, venomEffect, can cause severe allergic reactions in humans]
-
A.
venomous
Indicates that an organism possesses venom and can inject or deliver it to another organism, typically as a means of defense or predation.
-
B.
venomFunction
chosen
Indicates the specific biological role or effect that a venom has when acting on a target.
-
C.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
D.
involvedPhysicalEffect
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
E.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec2417648190ad010189d304d119 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.