Triple

T2877247
Position Surface form Disambiguated ID Type / Status
Subject Kumbhalgarh Fort E56906 entity
Predicate nearestCity P350 FINISHED
Object Udaipur E60736 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: Udaipur | Statement: [Kumbhalgarh Fort, nearestCity, Udaipur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Udaipur
Context triple: [Kumbhalgarh Fort, nearestCity, Udaipur]
  • A. Udaipur
    Udaipur is a historic town in the Indian state of Tripura, known for its ancient temples and scenic lakes.
  • B. Udaipur chosen
    Udaipur is a historic city in India renowned for its lakes, palaces, and role as a former capital of the Mewar kingdom.
  • C. Jaipur
    Jaipur is a major historic city in northwestern India, famed for its pink-hued architecture, royal palaces, and role as a key cultural and tourist center.
  • D. Jodhpur
    Jodhpur is a historic city in the Indian state of Rajasthan, renowned for its blue-painted old town, imposing Mehrangarh Fort, and role as a major cultural and commercial center on the edge of the Thar Desert.
  • E. Chittorgarh
    Chittorgarh is a historic city in Rajasthan, India, renowned for its massive hilltop fort, tales of Rajput valor, and rich cultural traditions.
  • 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abe007329c8190b0bc1851c7307124 completed March 7, 2026, 8:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69b37383fbf881909361d448de3c266b completed March 13, 2026, 2:16 a.m.
Created at: March 6, 2026, 10:03 p.m.