Triple
T31578359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vandellia |
E805755
|
entity |
| Predicate | bloodFeedingMechanism |
P84287
|
FINISHED |
| Object | attaches to gill filaments and feeds on blood |
—
|
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: attaches to gill filaments and feeds on blood | Statement: [Vandellia, bloodFeedingMechanism, attaches to gill filaments and feeds on blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodFeedingMechanism Context triple: [Vandellia, bloodFeedingMechanism, attaches to gill filaments and feeds on blood]
-
A.
obtainsBloodFrom
Indicates that one entity receives or collects blood from another entity.
-
B.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
C.
notableFeedingBehavior
chosen
Indicates a characteristic way or pattern in which an entity typically obtains or consumes food that is considered distinctive or noteworthy.
-
D.
bloodlust
Indicates an intense, often uncontrollable desire to shed blood or commit violent harm.
-
E.
hasLarvalDiet
Indicates the type of food or feeding behavior an organism relies on during its larval stage.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8068ca0819098f9f0195b0eb125 |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:22 p.m.