Triple
T1545714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gila monster |
E32971
|
entity |
| Predicate | venomDelivery |
P22947
|
FINISHED |
| Object | grooved teeth in lower jaw |
—
|
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: grooved teeth in lower jaw | Statement: [Gila monster, venomDelivery, grooved teeth in lower jaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venomDelivery Context triple: [Gila monster, venomDelivery, grooved teeth in lower jaw]
-
A.
venomous
chosen
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
Indicates the specific biological role or effect that a venom has when acting on a target.
-
C.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
D.
preysOn
Indicates that one entity hunts, kills, and consumes another entity as a food source.
-
E.
lionArmedAndLangued
Indicates that a lion is depicted with its claws and tongue emphasized, typically by being shown and colored distinctly.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.