Triple

T4664213
Position Surface form Disambiguated ID Type / Status
Subject Morena E102805 entity
Predicate hasNearbyCity P350 FINISHED
Object Dholpur E238055 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: Dholpur | Statement: [Morena, hasNearbyCity, Dholpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dholpur
Context triple: [Morena, hasNearbyCity, Dholpur]
  • A. Dholpur chosen
    Dholpur is a city in the Indian state of Rajasthan, known for its red sandstone, historical forts, and location near the Chambal ravines.
  • B. Madhepura
    Madhepura is a town and district headquarters in the eastern Indian state of Bihar, known for its agricultural economy and regional administrative importance.
  • C. Pratapgarh
    Pratapgarh is a town in the Indian state of Rajasthan known for its historical association with the Mewar region and its distinctive tribal culture and handicrafts.
  • D. Vidisha
    Vidisha is a historic city in the central Indian state of Madhya Pradesh, known for its ancient Buddhist and Hindu heritage and archaeological sites.
  • E. Hajipur
    Hajipur is a prominent city in the Indian state of Bihar, known as an important railway and commercial hub located near the state capital, Patna.
  • 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_69bd43d9cba4819086c1ab1c2d9d2133 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd633aeba88190a8329ed022d685b6 completed March 20, 2026, 3:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69be03803a948190b6dc2a03bb9cdc93 completed March 21, 2026, 2:33 a.m.
Created at: March 20, 2026, 1:15 p.m.