Triple
T21675178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediterranean diet |
E534946
|
entity |
| Predicate | fatComposition |
P40978
|
FINISHED |
| Object | high monounsaturated-to-saturated fat ratio |
—
|
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 monounsaturated-to-saturated fat ratio | Statement: [Mediterranean diet, fatComposition, high monounsaturated-to-saturated fat ratio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatComposition Context triple: [Mediterranean diet, fatComposition, high monounsaturated-to-saturated fat ratio]
-
A.
fatDistribution
Indicates how body fat is spatially allocated or spread across different regions of an entity.
-
B.
typicalFatContent
Indicates the usual or characteristic amount of fat contained in something, such as a food or product.
-
C.
fattyAcid
Indicates a relationship where one entity is a fatty acid component, derivative, or participant in a process involving another entity.
-
D.
fatStorage
Indicates the process or state in which an organism or system accumulates and retains fat as an energy reserve.
-
E.
typicalFatUsed
chosen
Indicates that a particular type of fat is commonly or characteristically used in a given context or application.
- 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.