Triple

T20183739
Position Surface form Disambiguated ID Type / Status
Subject Tulu Nadu E492799 entity
Predicate hasMajorTown P316 FINISHED
Object Bantwal 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: Bantwal | Statement: [Tulu Nadu, hasMajorTown, Bantwal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bantwal
Context triple: [Tulu Nadu, hasMajorTown, Bantwal]
  • A. Bantwal chosen
    Bantwal is a town in the Dakshina Kannada region of Karnataka, India, known historically as a commercial center on the banks of the Netravati River.
  • B. Bhatkal
    Bhatkal is a historic coastal town in Karnataka, India, known for its Arabian Sea shoreline, trading legacy, and distinctive Nawayath Muslim culture.
  • C. Sullia
    Sullia is a town in the Dakshina Kannada district of Karnataka, India, known as a local commercial and educational center in the region.
  • D. Gadag
    Gadag is a historic town in Karnataka, India, renowned for its richly carved medieval temples and monuments from the Western Chalukya architectural tradition.
  • E. Belthangady
    Belthangady is a town in the Dakshina Kannada district of Karnataka, India, known as a local commercial and administrative center in the region.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e668f068748190a0941e98ef5afd59 completed April 20, 2026, 5:57 p.m.
Created at: April 11, 2026, 11:36 p.m.