Triple

T15496734
Position Surface form Disambiguated ID Type / Status
Subject Gumbaz, Srirangapatna E378836 entity
Predicate locatedIn P40 FINISHED
Object Srirangapatna E64345 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: Srirangapatna | Statement: [Gumbaz, Srirangapatna, locatedIn, Srirangapatna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Srirangapatna
Context triple: [Gumbaz, Srirangapatna, locatedIn, Srirangapatna]
  • A. Srirangapatna chosen
    Srirangapatna is a historic island town in Karnataka, India, renowned as the former capital of Tipu Sultan and the Mysore Kingdom.
  • B. Nayandahalli
    Nayandahalli is a locality in southwestern Bangalore known as a key junction and residential area along major transport routes.
  • C. Pavagada
    Pavagada is a town in the Tumakuru district of Karnataka, India, known for its large solar park and semi-arid landscape.
  • D. Chamarajpet
    Chamarajpet is one of the oldest residential and commercial localities in Bengaluru, known for its traditional markets, historic temples, and dense urban character.
  • E. Gorikot
    Gorikot is a village and local hub in Pakistan’s Astore Valley, serving as a gateway to nearby mountain regions and trekking routes.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03faecd60819091eeaa56c9c8f67d completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d48f17c819088c4d8c2d2b368c8 completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 3:52 a.m.