Triple

T11740118
Position Surface form Disambiguated ID Type / Status
Subject Mewar region E279129 entity
Predicate hasMajorCity P316 FINISHED
Object Pratapgarh E289789 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: Pratapgarh | Statement: [Mewar region, hasMajorCity, Pratapgarh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pratapgarh
Context triple: [Mewar region, hasMajorCity, Pratapgarh]
  • A. Pratapgarh chosen
    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.
  • B. Pratapgarh city
    Pratapgarh city is an urban center in the Indian state of Uttar Pradesh known for serving as a local hub of administration, trade, and services for the surrounding region.
  • C. Anupgarh
    Anupgarh is a town in the Ganganagar district of Rajasthan, India, known for its agricultural surroundings and proximity to the India–Pakistan border.
  • D. Jalore
    Jalore is a historic town and district headquarters in the Indian state of Rajasthan, known for its ancient fort and role in the Marwar region’s history.
  • E. Madhepura
    Madhepura is a town and district headquarters in the eastern Indian state of Bihar, known for its agricultural economy and regional administrative importance.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4f025f88190a39280806c9d7c33 completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f16679c0ec81909fe80d75dd582db1 completed April 29, 2026, 2:01 a.m.
Created at: April 8, 2026, 9:41 p.m.