Triple
T8710775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enkutatash |
E206768
|
entity |
| Predicate | foodTraditions |
P19483
|
FINISHED |
| Object | injera with various stews |
—
|
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: injera with various stews | Statement: [Enkutatash, foodTraditions, injera with various stews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodTraditions Context triple: [Enkutatash, foodTraditions, injera with various stews]
-
A.
traditionalCuisine
Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
-
B.
haveDistinctCulinaryTraditions
Indicates that the related entities possess different and distinguishable culinary practices, cuisines, or food-related customs from one another.
-
C.
traditionalDish
chosen
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
D.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
-
E.
foodPreparationStyle
Indicates the manner or method by which food is prepared, cooked, or processed.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3189f88190bb9bb77ba9d28d60 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.