Triple

T15822879
Position Surface form Disambiguated ID Type / Status
Subject Bengaluru railway network E383655 entity
Predicate connectsToCity P4245 FINISHED
Object Jaipur E59514 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: Jaipur | Statement: [Bengaluru railway network, connectsToCity, Jaipur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jaipur
Context triple: [Bengaluru railway network, connectsToCity, Jaipur]
  • A. Jaipur chosen
    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.
  • B. 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.
  • C. Udaipur
    Udaipur is a historic town in the Indian state of Tripura, known for its ancient temples and scenic lakes.
  • D. Udaipur
    Udaipur is a town in the Lahaul and Spiti district of Himachal Pradesh, India, known for its scenic Himalayan setting and the ancient Mrikula Devi Temple.
  • E. Udaipur
    Udaipur is a historic city in India renowned for its lakes, palaces, and role as a former capital of the Mewar kingdom.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0c4a96b848190845cf547034a24f2 completed April 16, 2026, 11:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffb038dac881909ede37fa7766a249 completed May 9, 2026, 10:07 p.m.
Created at: April 10, 2026, 4:49 a.m.