Triple

T11837520
Position Surface form Disambiguated ID Type / Status
Subject Sawai Madhopur E281555 entity
Predicate hasVidhanSabhaConstituency P23217 FINISHED
Object Sawai Madhopur E281555 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: Sawai Madhopur | Statement: [Sawai Madhopur, hasVidhanSabhaConstituency, Sawai Madhopur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sawai Madhopur
Context triple: [Sawai Madhopur, hasVidhanSabhaConstituency, Sawai Madhopur]
  • A. Sawai Madhopur chosen
    Sawai Madhopur is a town in Rajasthan, India, best known as the main gateway to the tiger-rich Ranthambore region and its historic fort.
  • B. Tonk–Sawai Madhopur
    Tonk–Sawai Madhopur is a parliamentary constituency in the Indian state of Rajasthan that elects a representative to the Lok Sabha.
  • C. Rampur
    Rampur is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • D. Rampur
    Rampur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known historically for its princely state heritage and distinctive Rampuri culture.
  • E. Sri Madhopur
    Sri Madhopur is a town in the Sikar district of Rajasthan, India, known for its historical significance and regional trade and agriculture.
  • 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_69d6ab276f8c8190b1966a0ef11349ac completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a62fec0881908c7b89c0b5bcc9a2 completed April 10, 2026, 7:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69f4583d9900819090be07726ed00b93 completed May 1, 2026, 7:37 a.m.
Created at: April 8, 2026, 9:43 p.m.