Triple
T19418150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornish clotted cream |
E485773
|
entity |
| Predicate | dietaryConsideration |
P135801
|
FINISHED |
| Object | high in saturated fat |
—
|
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 saturated fat | Statement: [Cornish clotted cream, dietaryConsideration, high in saturated fat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietaryConsideration Context triple: [Cornish clotted cream, dietaryConsideration, high in saturated fat]
-
A.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
-
B.
dietVersion
Indicates that one diet is a specific version, variant, or iteration of another diet.
-
C.
dietAdvocated
Indicates that one entity promotes, recommends, or supports a particular diet for another entity or audience.
-
D.
hasDietaryLaw
Indicates that one entity prescribes, follows, or is governed by a specific set of dietary rules or restrictions associated with 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62afad8d881908f1de6324e55d2f6 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.