Triple
T18175963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilopoda |
E435160
|
entity |
| Predicate | usesVenomFor |
P116077
|
FINISHED |
| Object | subduingPrey |
—
|
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: subduingPrey | Statement: [Chilopoda, usesVenomFor, subduingPrey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVenomFor Context triple: [Chilopoda, usesVenomFor, subduingPrey]
-
A.
venomDeliverySystem
Indicates the mechanism or method by which venom is produced, stored, and transferred from one organism to another.
-
B.
venomPotency
Indicates the degree of strength or toxicity of an entity’s venom in affecting another entity.
-
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.
poisonUsed
chosen
Indicates that one entity employed poison as a means to harm, kill, or incapacitate another entity.
-
E.
containsVenomousSpecies
Indicates that the referenced entity includes within it one or more species that are venomous.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df59bf3881909adc28cacbe9cb39 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.