Triple
T34488981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dubrow Diet |
E885413
|
entity |
| Predicate | limitsMacronutrient |
P179417
|
FINISHED |
| Object | carbohydrates |
—
|
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: carbohydrates | Statement: [The Dubrow Diet, limitsMacronutrient, carbohydrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitsMacronutrient Context triple: [The Dubrow Diet, limitsMacronutrient, carbohydrates]
-
A.
calorieProfile
Indicates the relationship between an entity and the detailed breakdown of its caloric characteristics, such as total calories and their distribution.
-
B.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
-
C.
calorieLevel
Indicates the relationship between an entity and the amount of calories it contains or provides, typically categorized by intensity or range (e.g., low, medium, high).
-
D.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
E.
hasCalories
Indicates that an entity contains a specified amount of caloric energy.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 2:01 a.m.