Triple
T36225091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aje Alekwu festival |
E1047961
|
entity |
| Predicate | foodRole |
P7171
|
FINISHED |
| Object | sharing of traditional Idoma dishes |
—
|
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: sharing of traditional Idoma dishes | Statement: [Aje Alekwu festival, foodRole, sharing of traditional Idoma dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodRole Context triple: [Aje Alekwu festival, foodRole, sharing of traditional Idoma dishes]
-
A.
roleInFood
Indicates the functional role or purpose that an entity has within a food item, product, or context (e.g., ingredient, flavoring, preservative).
-
B.
foodCustom
chosen
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
C.
foodService
Indicates that one entity provides, manages, or is responsible for supplying food or meal-related services to another entity.
-
D.
worksInKitchenAt
Indicates that an entity performs work or duties in the kitchen area of a specified location or organization.
-
E.
knownForDish
Indicates that an entity is recognized or notable for preparing, serving, or being associated with a particular dish.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b583a72481908411abb0daeb9f2d |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.