Triple
T1798795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genlisea |
E39665
|
entity |
| Predicate | nutrientAcquisition |
P14752
|
FINISHED |
| Object | supplements nutrients by carnivory |
—
|
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: supplements nutrients by carnivory | Statement: [Genlisea, nutrientAcquisition, supplements nutrients by carnivory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nutrientAcquisition Context triple: [Genlisea, nutrientAcquisition, supplements nutrients by carnivory]
-
A.
nutrientUptake
chosen
Indicates the process by which an entity absorbs or takes in nutrients from its surrounding environment.
-
B.
foragingStratum
Indicates the vertical layer or height within a habitat where an organism typically searches for and obtains its food.
-
C.
foragingStrategy
Indicates the method or pattern an organism uses to search for, obtain, and exploit food resources.
-
D.
receivesMoistureFrom
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
-
E.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.