Triple
T21675133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediterranean diet |
E534946
|
entity |
| Predicate | emphasizesFatType |
P40978
|
FINISHED |
| Object | monounsaturated 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: monounsaturated fat | Statement: [Mediterranean diet, emphasizesFatType, monounsaturated fat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesFatType Context triple: [Mediterranean diet, emphasizesFatType, monounsaturated fat]
-
A.
typicalFatContent
Indicates the usual or characteristic amount of fat contained in something, such as a food or product.
-
B.
fatDistribution
Indicates how body fat is spatially allocated or spread across different regions of an entity.
-
C.
typicalFatUsed
chosen
Indicates that a particular type of fat is commonly or characteristically used in a given context or application.
-
D.
fattyAcid
Indicates a relationship where one entity is a fatty acid component, derivative, or participant in a process involving another entity.
-
E.
traditionalFat
Indicates that an entity uses or contains a type or amount of fat characteristic of customary or long-established practices.
- 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_69ef8a0ed5388190b8f1932fb3f11c6a |
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:41 p.m.