Triple

T21886893
Position Surface form Disambiguated ID Type / Status
Subject Pajaka E540427 entity
Predicate near P350 FINISHED
Object Udupi 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: Udupi | Statement: [Pajaka, near, Udupi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Udupi
Context triple: [Pajaka, near, Udupi]
  • A. Udupi chosen
    Udupi is a coastal city in the Indian state of Karnataka, renowned for its historic Krishna temple, distinctive Udupi cuisine, and cultural and educational institutions.
  • B. Belthangady
    Belthangady is a town in the Dakshina Kannada district of Karnataka, India, known as a local commercial and administrative center in the region.
  • C. Hubli
    Hubli is a major commercial and transportation hub in the Indian state of Karnataka, known for its busy railway junction and growing industrial economy.
  • D. Kuppali
    Kuppali is a village in the Indian state of Karnataka, best known as the birthplace and childhood home of the renowned Kannada writer Kuvempu (Kuppali Venkatappa Puttappa).
  • E. Tharangambadi
    Tharangambadi is a historic coastal town in Tamil Nadu, India, known for its former Danish colonial settlement, seaside fort, and blend of Indian and European heritage.
  • 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_69e0c47a95908190ae3e19b716accb3d completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f118ed35948190bbffba2c40029eee completed April 28, 2026, 8:30 p.m.
Created at: April 16, 2026, 7:05 p.m.