Triple

T16964514
Position Surface form Disambiguated ID Type / Status
Subject Kannada people E411508 entity
Predicate traditionalCuisine P1016 FINISHED
Object Mysore pak E632256 NE 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: Mysore pak | Statement: [Kannada people, traditionalCuisine, Mysore pak]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mysore pak
Context triple: [Kannada people, traditionalCuisine, Mysore pak]
  • A. Mysore Pak chosen
    Mysore Pak is a rich South Indian sweet made primarily from ghee, sugar, and gram flour, traditionally associated with royal Mysuru cuisine and festive occasions.
  • B. Kolhapuri Misal
    Kolhapuri Misal is a spicier, fiery version of the traditional Maharashtrian misal pav, originating from Kolhapur and known for its robust, chili-forward gravy.
  • C. Dharwad peda
    Dharwad peda is a famous traditional Indian milk-based sweet delicacy originating from the city of Dharwad in Karnataka.
  • D. Mulam
    Mulam is an ethnic minority group in southern China, primarily residing in Guangxi, known for its Kam–Sui language and distinct traditional culture.
  • E. Basopatti
    Basopatti is a town located in the Madhubani district of the Indian state of Bihar.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0a2cda88190bd574a869f0e43e9 completed April 18, 2026, 6:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00d46cb56481908c2bc6648a12fbcf completed May 10, 2026, 6:54 p.m.
Created at: April 10, 2026, 5:31 a.m.