Triple
T5607753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lean Cuisine |
E147273
|
entity |
| Predicate | dietaryPositioning |
P3602
|
FINISHED |
| Object | calorie-controlled |
—
|
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: calorie-controlled | Statement: [Lean Cuisine, dietaryPositioning, calorie-controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietaryPositioning Context triple: [Lean Cuisine, dietaryPositioning, calorie-controlled]
-
A.
nutritionType
chosen
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
B.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
-
C.
nutritionStandard
Indicates that something complies with, or is evaluated against, a defined set of nutritional guidelines or requirements.
-
D.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fd1b2c81908da154f7e11b90d8 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.