Triple
T289608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insectivorous Plants |
E5959
|
entity |
| Predicate | investigates |
P1857
|
FINISHED |
| Object | nutrient uptake from animal prey |
—
|
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: nutrient uptake from animal prey | Statement: [Insectivorous Plants, investigates, nutrient uptake from animal prey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigates Context triple: [Insectivorous Plants, investigates, nutrient uptake from animal prey]
-
A.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
B.
explores
chosen
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
C.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
-
D.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
E.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4df5508190ab75115ac6b3964e |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7d089081909810442c3d0182f6 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.