Triple

T21641205
Position Surface form Disambiguated ID Type / Status
Subject Middle Eastern cuisine E534090 entity
Predicate hasDish P17589 FINISHED
Object kofta 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: kofta | Statement: [Middle Eastern cuisine, hasDish, kofta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: kofta
Context triple: [Middle Eastern cuisine, hasDish, kofta]
  • A. KOFA
    KOFA is the commonly used abbreviation for the historic King of Arizona Mine, a notable gold mining operation in Arizona.
  • B. Kofetarica
    Kofetarica is a well-known Slovenian painting, celebrated as a classic work of national art and housed in the National Gallery of Slovenia.
  • C. Kofte chosen
    Kofte is a popular Middle Eastern and South Asian-style meatball or minced meat patty, often seasoned with herbs and spices and grilled, fried, or baked.
  • D. kös
    Kös is a large traditional Ottoman-Turkish kettledrum used in military bands, especially in ceremonial mehter music.
  • E. Kotputli
    Kotputli is a town in the Indian state of Rajasthan that serves as an important commercial and transport hub between Jaipur and Delhi.
  • 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.