Triple
T21675175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediterranean diet |
E534946
|
entity |
| Predicate | macronutrientPattern |
P3602
|
FINISHED |
| Object | moderate fat intake |
—
|
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: moderate fat intake | Statement: [Mediterranean diet, macronutrientPattern, moderate fat intake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: macronutrientPattern Context triple: [Mediterranean diet, macronutrientPattern, moderate fat intake]
-
A.
nutritionType
chosen
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
B.
nutritionMode
Indicates the way an entity obtains or processes nutrients for sustenance or growth.
-
C.
dietVersion
Indicates that one diet is a specific version, variant, or iteration of another diet.
-
D.
nutritionStandard
Indicates that something complies with, or is evaluated against, a defined set of nutritional guidelines or requirements.
-
E.
calorieProfile
Indicates the relationship between an entity and the detailed breakdown of its caloric characteristics, such as total calories and their distribution.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0f85748190944b9425ffed02ee |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:42 p.m.