Triple

T20412265
Position Surface form Disambiguated ID Type / Status
Subject Salasar Balaji E500613 entity
Predicate hasNearbyCity P350 FINISHED
Object Sikar 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: Sikar | Statement: [Salasar Balaji, hasNearbyCity, Sikar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sikar
Context triple: [Salasar Balaji, hasNearbyCity, Sikar]
  • A. Sikar chosen
    Sikar is a prominent city in northern India known for its historic havelis, educational institutions, and role as a commercial hub in the Shekhawati region.
  • B. Sakesar
    Sakesar is a prominent mountain peak in Pakistan’s Punjab region, known for its scenic views, cooler climate, and strategic location within the Salt Range.
  • C. Sachkhere
    Sachkhere is a town in western Georgia known as a local administrative and economic center in the Imereti region.
  • D. Sonpur
    Sonpur is a town in the Indian state of Bihar, known for its location near the confluence of the Ganges and Gandak rivers and for hosting one of Asia’s largest traditional cattle fairs.
  • E. Nangal
    Nangal is a town in the Rupnagar district of Punjab, India, known for its proximity to the Bhakra-Nangal Dam and the Gobind Sagar Lake on the Sutlej 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_69e0b4a935588190b9446a99b37ced44 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67a3f8fdc8190b05b6c41b38f34b7 completed April 20, 2026, 7:10 p.m.
Created at: April 16, 2026, 11:30 a.m.