Triple

T3357981
Position Surface form Disambiguated ID Type / Status
Subject HITEC City E70649 entity
Predicate adjacentTo P224 FINISHED
Object Madhapur E349850 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: Madhapur | Statement: [HITEC City, adjacentTo, Madhapur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Madhapur
Context triple: [HITEC City, adjacentTo, Madhapur]
  • A. Madhapur chosen
    Madhapur is a major IT and business district in Hyderabad, India, known for its technology parks, corporate offices, and modern urban infrastructure.
  • B. Damoh
    Damoh is a city in central India that serves as the administrative headquarters of Damoh district in the state of Madhya Pradesh.
  • C. Jaipuri
    Jaipuri is a regional Indo-Aryan language variety spoken in and around Jaipur in the Indian state of Rajasthan.
  • D. Budaun
    Budaun is a historic city in the Rohilkhand region of Uttar Pradesh, India, known for its medieval heritage and cultural significance.
  • E. Warangal
    Warangal is a historic city in southern India known for its Kakatiya-era forts, temples, and monuments, and is one of the major urban centers of the state of Telangana.
  • 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_69ad85a660c48190998489309a3b4869 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb244435c81908e35d2aa36ec4f46 completed March 8, 2026, 5:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3253e91988190bbfdafdf88ab0df1 completed March 12, 2026, 8:42 p.m.
Created at: March 8, 2026, 3:13 p.m.