Triple
T9021156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharchi Puja |
E215724
|
entity |
| Predicate | foodAspect |
P7171
|
FINISHED |
| Object | preparation of special festive foods |
—
|
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: preparation of special festive foods | Statement: [Kharchi Puja, foodAspect, preparation of special festive foods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodAspect Context triple: [Kharchi Puja, foodAspect, preparation of special festive foods]
-
A.
foodCustom
chosen
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
B.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
-
C.
foodItem
Indicates that one entity is a food item that can be eaten or used as food in relation to another entity.
-
D.
favoriteFood
Indicates that one entity has a preferred or most liked food item in relation to another entity or context.
-
E.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a43add08190983b7ac88576fd7e |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.