Triple

T11277593
Position Surface form Disambiguated ID Type / Status
Subject Tipu Sultan E266975 entity
Predicate birthPlace P1 FINISHED
Object Devanahalli E340565 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: Devanahalli | Statement: [Tipu Sultan, birthPlace, Devanahalli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Devanahalli
Context triple: [Tipu Sultan, birthPlace, Devanahalli]
  • A. Devanahalli chosen
    Devanahalli is a town near Bengaluru in the Indian state of Karnataka, notable for its rapid development and proximity to Kempegowda International Airport.
  • B. Kollur
    Kollur is a village in Karnataka, India, best known for the Mookambika Temple, a major Hindu pilgrimage destination.
  • C. Gorikot
    Gorikot is a village and local hub in Pakistan’s Astore Valley, serving as a gateway to nearby mountain regions and trekking routes.
  • D. Sindhanur
    Sindhanur is a town in Karnataka, India, known primarily for its extensive paddy cultivation and role as a major rice-producing center.
  • E. Lakkundi
    Lakkundi is a historic village in Karnataka, India, renowned for its intricately carved medieval temples and stepwells built during the Western Chalukya period.
  • 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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e967ebb4819080b09ed3cec44e77 completed April 9, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4f455f0bc8190994c57264f775f60 completed April 19, 2026, 3:27 p.m.
Created at: April 8, 2026, 9:31 p.m.