Triple
T33841102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensure Max Protein |
E867359
|
entity |
| Predicate | hasNutrientProfile |
P111435
|
FINISHED |
| Object | high protein |
—
|
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: high protein | Statement: [Ensure Max Protein, hasNutrientProfile, high protein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNutrientProfile Context triple: [Ensure Max Protein, hasNutrientProfile, high protein]
-
A.
hasNutrientStatus
Indicates that an entity possesses a particular nutritional condition or level, such as being deficient, sufficient, or excessive in specific nutrients.
-
B.
hasNutrientContent
chosen
Indicates that one entity contains or provides a specified amount or type of nutrient relative to another entity or standard.
-
C.
hasAssociatedNutrient
Indicates that one entity is linked to or contains a specific nutrient as part of its nutritional composition or association.
-
D.
hasNutritionalConcern
Indicates that an entity is associated with a specific nutritional issue, risk, or dietary concern.
-
E.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 1, 2026, 1:47 a.m.