Triple
T28855487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byblidaceae |
E728721
|
entity |
| Predicate | recognizedAsCarnivorousPlantFamily |
P42709
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Byblidaceae, recognizedAsCarnivorousPlantFamily, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsCarnivorousPlantFamily Context triple: [Byblidaceae, recognizedAsCarnivorousPlantFamily, true]
-
A.
isCarnivorousPlantFamily
chosen
Indicates that a plant family is characterized by species that derive some or most of their nutrients by trapping and consuming animals or other small organisms.
-
B.
carnivoryType
Indicates the specific manner or strategy by which an organism engages in carnivory (i.e., how it feeds on animal prey).
-
C.
carnivorousType
Indicates that one entity is a type or category of organism that feeds primarily on other animals (is carnivorous).
-
D.
isCarnivorous
Indicates that an entity feeds primarily or exclusively on other animals.
-
E.
hasSucculentMembers
Indicates that a group or category includes one or more members that are succulents.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 6:45 a.m.