Triple
T433213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajasthan |
E9756
|
entity |
| Predicate | traditionalCuisineItem |
P6863
|
FINISHED |
| Object | dal baati churma |
—
|
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: dal baati churma | Statement: [Rajasthan, traditionalCuisineItem, dal baati churma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCuisineItem Context triple: [Rajasthan, traditionalCuisineItem, dal baati churma]
-
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.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
C.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
D.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
E.
cuisine
chosen
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef084840819080653004b674cba8 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2edda55e88190b7c17ba94d7df1ce |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.