Triple

T21641111
Position Surface form Disambiguated ID Type / Status
Subject Indian cuisine E534089 entity
Predicate hasDish P17589 FINISHED
Object bhel puri NE NERFINISHED

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: bhel puri | Statement: [Indian cuisine, hasDish, bhel puri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: bhel puri
Context triple: [Indian cuisine, hasDish, bhel puri]
  • A. Kanchipuri
    Kanchipuri is another name for Kanchipuram, an ancient South Indian city renowned for its historic temples and silk saree weaving tradition.
  • B. Khichdi chosen
    Khichdi is a traditional South Asian comfort dish made by cooking rice and lentils together, often seasoned with mild spices and ghee.
  • C. Chakola
    Chakola is a small rural locality in New South Wales, Australia, situated in the Monaro region.
  • D. Loghoma
    Loghoma is an alternative name for the Loma people, an ethnic group primarily found in Liberia and neighboring West African regions.
  • E. Rozogi
    Rozogi is a village in northern Poland that serves as a local administrative and service center within the Warmian-Masurian Voivodeship.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c465ae7481908577b7209fdb2a77 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef53917f3c81909e7f4074beecefd3 completed April 27, 2026, 12:16 p.m.
Created at: April 16, 2026, 6:35 p.m.