Triple

T19691591
Position Surface form Disambiguated ID Type / Status
Subject Chunky E472846 entity
Predicate hasNutritionalPositioning P111435 FINISHED
Object high in protein (varies by variety) 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 in protein (varies by variety) | Statement: [Chunky, hasNutritionalPositioning, high in protein (varies by variety)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNutritionalPositioning
Context triple: [Chunky, hasNutritionalPositioning, high in protein (varies by variety)]
  • 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. hasPositionInDiet
    Indicates the relative role or ranking that something occupies within a diet or dietary plan.
  • D. regulatesNutrient
    Indicates a relationship where one entity controls, modulates, or maintains the levels, availability, or flow of a nutrient in another entity or system.
  • E. nutritionType
    Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
  • 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_69d8e515bef88190bc30781aea50537a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6421013c4819095e80aadfe590102 completed April 20, 2026, 3:11 p.m.
PD Predicate disambiguation batch_69e53039ea808190a9106a53f564ab92 completed April 19, 2026, 7:42 p.m.
Created at: April 10, 2026, 1:46 p.m.