Triple

T19273261
Position Surface form Disambiguated ID Type / Status
Subject Trimulgherry E481981 entity
Predicate nearbyLocality P4647 FINISHED
Object Bolarum NE NERFINISHED

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: Bolarum | Statement: [Trimulgherry, nearbyLocality, Bolarum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bolarum
Context triple: [Trimulgherry, nearbyLocality, Bolarum]
  • A. Bolarum chosen
    Bolarum is a suburban residential and cantonment area in the northern part of Hyderabad, India, known for its military establishments and colonial-era buildings.
  • B. Tadipatri
    Tadipatri is a town in the Anantapur district of Andhra Pradesh, India, known for its granite industries and historic temples.
  • C. Allagadda
    Allagadda is a town and legislative assembly constituency in the Nandyal district of Andhra Pradesh, India.
  • D. Guntakal
    Guntakal is a major railway junction town in Andhra Pradesh, India, serving as an important transit hub on several key rail routes in southern India.
  • E. Mandapeta
    Mandapeta is a town in the East Godavari region of Andhra Pradesh, India, known for its agricultural economy and proximity to the Godavari River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8ce54cc8190998418ff1f66ef28 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fbba7758819081c1c78667c59c5e completed April 20, 2026, 10:11 a.m.
Created at: April 10, 2026, 1:29 p.m.