Triple

T14875396
Position Surface form Disambiguated ID Type / Status
Subject Kokapet E349853 entity
Predicate locatedNear P294 FINISHED
Object Gandipet E359035 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: Gandipet | Statement: [Kokapet, locatedNear, Gandipet]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gandipet
Context triple: [Kokapet, locatedNear, Gandipet]
  • A. Gandipet chosen
    Gandipet is a locality on the outskirts of Hyderabad, India, best known for the nearby Osman Sagar (Gandipet Lake) and its popular lakeside recreational areas.
  • B. Gachibowli
    Gachibowli is a major IT and residential hub in Hyderabad, India, known for its technology parks, corporate offices, and educational institutions.
  • C. Kadugodi
    Kadugodi is a suburban neighborhood in the eastern part of Bengaluru, India, known for its residential areas, markets, and proximity to major IT and industrial hubs.
  • D. 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.
  • E. Bachupally
    Bachupally is a rapidly developing residential and educational suburb in the northwestern part of Hyderabad, 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded5e3e5d48190a132f2cf012b01e2 completed April 15, 2026, 12:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe9dbf1f5c8190ad4626d14e0d8109 completed May 9, 2026, 2:36 a.m.
Created at: April 10, 2026, 1:55 a.m.