Triple
T34707064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roridulaceae |
E1000534
|
entity |
| Predicate | nutrientsObtainedFrom |
P181714
|
FINISHED |
| Object | insect excreta |
—
|
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: insect excreta | Statement: [Roridulaceae, nutrientsObtainedFrom, insect excreta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nutrientsObtainedFrom Context triple: [Roridulaceae, nutrientsObtainedFrom, insect excreta]
-
A.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
-
B.
nutritionalRequirement
Indicates that one entity has a need for certain nutrients or dietary conditions that must be met by another entity or resource.
-
C.
hasNutrientContent
Indicates that one entity contains or provides a specified amount or type of nutrient relative to another entity or standard.
-
D.
isEssentialNutrientFor
Indicates that one entity is a nutrient required for the normal growth, function, or survival of another entity.
-
E.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.