Triple
T18175962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilopoda |
E435160
|
entity |
| Predicate | forcipulesFunction |
P130754
|
FINISHED |
| Object | venomDelivery |
—
|
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: venomDelivery | Statement: [Chilopoda, forcipulesFunction, venomDelivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcipulesFunction Context triple: [Chilopoda, forcipulesFunction, venomDelivery]
-
A.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
B.
inForce
Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
-
C.
forceElement
Indicates a physical or conceptual force acting upon, influencing, or constraining another element within a system or interaction.
-
D.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
E.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:30 a.m.