Triple

T14518531
Position Surface form Disambiguated ID Type / Status
Subject Kalaburagi Bench E340588 entity
Predicate locatedIn P40 FINISHED
Object Kalaburagi E178842 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: Kalaburagi | Statement: [Kalaburagi Bench, locatedIn, Kalaburagi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kalaburagi
Context triple: [Kalaburagi Bench, locatedIn, Kalaburagi]
  • A. Kalaburagi chosen
    Kalaburagi is a major city in the northern part of the Indian state of Karnataka, known historically as Gulbarga and noted for its rich heritage and architectural monuments from the Bahmani Sultanate era.
  • B. Khammam
    Khammam is a city in the Indian state of Telangana known for its historical forts, temples, and proximity to the Munneru River.
  • C. Jangaon
    Jangaon is a town and municipal center in the Indian state of Telangana, known for its location along key road and rail routes between Hyderabad and Warangal.
  • D. Guntur
    Guntur is a volcanic mountain in West Java, Indonesia, known for its geothermal activity and scenic hiking routes.
  • E. Guntur
    Guntur is a major city in the Indian state of Andhra Pradesh, known historically as an important administrative and commercial center in southeastern India.
  • 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_69d822d9c0408190b9a2b3643e58bb4d completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69de9a70b15c81908773633e989ef704 completed April 14, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69fde16666b8819090fb33c71515ab0a completed May 8, 2026, 1:13 p.m.
Created at: April 10, 2026, 1:22 a.m.