Triple

T14875349
Position Surface form Disambiguated ID Type / Status
Subject Manikonda E349852 entity
Predicate near P350 FINISHED
Object Raidurg E350660 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: Raidurg | Statement: [Manikonda, near, Raidurg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raidurg
Context triple: [Manikonda, near, Raidurg]
  • A. Raidurg chosen
    Raidurg is a rapidly developing commercial and residential neighborhood in Hyderabad’s IT hub, known for its proximity to major tech parks and infrastructure in the Cyberabad area.
  • B. Radaur
    Radaur is a town in the Yamunanagar district of Haryana, India, known primarily as a local commercial and educational center for surrounding rural areas.
  • C. Rausu
    Rausu is a small coastal town on Japan’s Shiretoko Peninsula, known for its rich marine wildlife, drift ice sightseeing, and access to the remote natural landscapes of eastern Hokkaido.
  • D. Riasti
    Riasti is a regional dialect of the Saraiki language spoken primarily in parts of southern Punjab, Pakistan.
  • E. Dargwa
    Dargwa is a Northeast Caucasian language spoken primarily by the Dargin people in the Republic of Dagestan, Russia.
  • 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_69fe6b52c12481908d0173a2a3ed854b completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 1:55 a.m.