Triple

T14249457
Position Surface form Disambiguated ID Type / Status
Subject Miyapur E353218 entity
Predicate nearbyLocality P4647 FINISHED
Object Kukatpally E1090349 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: Kukatpally | Statement: [Miyapur, nearbyLocality, Kukatpally]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kukatpally
Context triple: [Miyapur, nearbyLocality, Kukatpally]
  • A. Kukatpally chosen
    Kukatpally is a major residential and commercial suburb in Hyderabad, India, known for its dense population, shopping areas, and proximity to the IT corridor.
  • B. Dundigal
    Dundigal is a suburban area near Hyderabad in Telangana, India, known primarily for hosting the Indian Air Force Academy.
  • C. Ravulapalem
    Ravulapalem is a town in the Indian state of Andhra Pradesh, known for its agricultural markets and location along key transport routes in the Godavari region.
  • D. Bhadrachalam
    Bhadrachalam is a temple town in Telangana, India, renowned for its major Sri Rama temple and its location along the banks of the Godavari River.
  • E. Kondapur
    Kondapur is a rapidly developing residential and commercial suburb in Hyderabad, India, known for its proximity to major IT hubs and tech parks.
  • 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_69d8278c43e08190824146f4632b89a5 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6295ef9081909cfb0c1283bca21a completed April 14, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd647b37a8819095fe0bb62e0373fb completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:08 a.m.