Triple

T11092931
Position Surface form Disambiguated ID Type / Status
Subject Kundapura E262300 entity
Predicate locatedNear P294 FINISHED
Object Udupi E885255 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: Udupi | Statement: [Kundapura, locatedNear, Udupi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Udupi
Context triple: [Kundapura, locatedNear, 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. 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.
  • E. Udupi district
    Udupi district is a coastal district in the Indian state of Karnataka, known for its temple town of Udupi, distinctive cuisine, and rich Tulu-Kannada cultural heritage.
  • 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_69d6aa9a40d88190a373e2c7e48285db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d799ed12d88190a4ad8c346d68f11f completed April 9, 2026, 12:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69e441bb14d08190ac01bf3daa34ae43 completed April 19, 2026, 2:45 a.m.
Created at: April 8, 2026, 9:27 p.m.