Triple

T14667879
Position Surface form Disambiguated ID Type / Status
Subject Ulsoor E344425 entity
Predicate nearbyLocality P4647 FINISHED
Object Indiranagar E983620 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: Indiranagar | Statement: [Ulsoor, nearbyLocality, Indiranagar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Indiranagar
Context triple: [Ulsoor, nearbyLocality, Indiranagar]
  • A. Indiranagar chosen
    Indiranagar is a prominent residential and commercial neighborhood in eastern Bengaluru, known for its upscale eateries, pubs, and shopping streets.
  • B. Mambai
    Mambai is an Austronesian language spoken primarily in East Timor, where it is one of the country’s major indigenous languages.
  • C. Bengaluru
    Bengaluru is a major Indian metropolis known as the country’s leading technology and innovation hub, often called the “Silicon Valley of India.”
  • D. Bhopal
    Bhopal is the capital city of the Indian state of Madhya Pradesh, known for its historic lakes, administrative importance, and the site of the 1984 industrial disaster.
  • E. Gandhinagar
    Gandhinagar is a planned city in western India known for serving as the administrative and political center of the state of Gujarat.
  • 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_69d822e283fc8190a0e4c235cf880052 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb54dda1c8190bf16d17e26a2bba6 completed April 14, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69febfcf67348190862c65faa1c815f0 completed May 9, 2026, 5:02 a.m.
Created at: April 10, 2026, 1:27 a.m.