Triple

T8526654
Position Surface form Disambiguated ID Type / Status
Subject Udaipur State E201834 entity
Predicate hasCity P316 FINISHED
Object Rajsamand E283745 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: Rajsamand | Statement: [Udaipur State, hasCity, Rajsamand]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajsamand
Context triple: [Udaipur State, hasCity, Rajsamand]
  • A. Rajsamand chosen
    Rajsamand is a town in the Indian state of Rajasthan, known for the nearby Rajsamand Lake and its historical association with the Mewar region.
  • B. Nadiad
    Nadiad is a city in the Indian state of Gujarat, historically notable as the birthplace of independence leader Sardar Vallabhbhai Patel.
  • C. Bathinda
    Bathinda is a major city in southwestern Punjab, India, known as an important agricultural, industrial, and military center with historical forts and thermal power plants.
  • D. Sant Kabir Nagar
    Sant Kabir Nagar is a district in the Purvanchal region of Uttar Pradesh, India, named after the 15th-century mystic poet-saint Kabir.
  • E. Yamunanagar
    Yamunanagar is an industrial city in the Indian state of Haryana, known for its plywood, paper, and metal industries and its proximity to the Yamuna River.
  • 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_69ca83228b24819085d22e7dc99f5d94 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe6463fe48190b6d3482212356be1 completed March 31, 2026, 3:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce6d49c1408190b7c23739409d1e3d completed April 2, 2026, 1:21 p.m.
Created at: March 30, 2026, 6:16 p.m.