Triple

T10736623
Position Surface form Disambiguated ID Type / Status
Subject Dakshina Kannada district E253210 entity
Predicate hasTown P847 FINISHED
Object Puttur E555171 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: Puttur | Statement: [Dakshina Kannada district, hasTown, Puttur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Puttur
Context triple: [Dakshina Kannada district, hasTown, Puttur]
  • A. Puttur
    Puttur is a town in the Indian state of Andhra Pradesh, known for its traditional bone-setting practices and regional commercial significance.
  • B. Puttur chosen
    Puttur is a prominent town in Karnataka’s Dakshina Kannada district, known for its educational institutions, temples, and role as a commercial hub in the region.
  • C. Puttu
    Puttu is a traditional South Indian steamed rice cake, typically cylindrical and layered with grated coconut, commonly eaten for breakfast in Kerala.
  • D. Sattenapalle
    Sattenapalle is a town in the Indian state of Andhra Pradesh, known as a local commercial and administrative center within the Guntur region.
  • E. Porul
    Porul is the second section of the ancient Tamil classic Tirukkural, focusing on ethics, governance, politics, and social conduct.
  • 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_69d6aa5e51e8819095f06881cecf152e completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d71022aee0819091a5790d3dee6777 completed April 9, 2026, 2:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69de22cc4edc8190a7ab45e57ed94c47 completed April 14, 2026, 11:19 a.m.
Created at: April 8, 2026, 9:14 p.m.