Triple
T28859182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxymonads |
E728813
|
entity |
| Predicate | nutrition |
P65196
|
FINISHED |
| Object | live in close association with gut microbiota |
—
|
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: live in close association with gut microbiota | Statement: [Oxymonads, nutrition, live in close association with gut microbiota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nutrition Context triple: [Oxymonads, nutrition, live in close association with gut microbiota]
-
A.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
B.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
C.
nutritionMode
chosen
Indicates the way an entity obtains or processes nutrients for sustenance or growth.
-
D.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
-
E.
focusesOnNutrition
Indicates that the subject’s primary attention, activity, or content is centered on nutrition-related topics, practices, or goals.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a14eaa081908113d246dbaf86dd |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:46 a.m.