Triple
T18414600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acciaroli |
E441852
|
entity |
| Predicate | dietPattern |
P112132
|
FINISHED |
| Object | traditional Mediterranean diet rich in olive oil and fish |
—
|
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: traditional Mediterranean diet rich in olive oil and fish | Statement: [Acciaroli, dietPattern, traditional Mediterranean diet rich in olive oil and fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietPattern Context triple: [Acciaroli, dietPattern, traditional Mediterranean diet rich in olive oil and fish]
-
A.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
B.
eatingHabit
chosen
Indicates a characteristic pattern or regularity in how an entity consumes food, such as what, when, or how it typically eats.
-
C.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
D.
dietVersion
Indicates that one diet is a specific version, variant, or iteration of another diet.
-
E.
dietAdvocated
Indicates that one entity promotes, recommends, or supports a particular diet for another entity or audience.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a26d268819098e6791dc98efcda |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.