Triple

T7241194
Position Surface form Disambiguated ID Type / Status
Subject Shajapur E155358 entity
Predicate historicalName P65 FINISHED
Object Shahjahanpur E280629 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: Shahjahanpur | Statement: [Shajapur, historicalName, Shahjahanpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shahjahanpur
Context triple: [Shajapur, historicalName, Shahjahanpur]
  • A. Shahjahanpur chosen
    Shahjahanpur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known for its historical significance and regional commercial importance.
  • B. Bulandshahr
    Bulandshahr is a city in the Indian state of Uttar Pradesh known for its historical significance and proximity to Delhi within the broader metropolitan region.
  • C. Jaunpur
    Jaunpur is a historic city in the Indian state of Uttar Pradesh, known for its medieval architecture and cultural heritage.
  • D. Moradabad
    Moradabad is a major city in northern India known for its brass handicraft industry and is located in the state of Uttar Pradesh.
  • E. Farrukhabad
    Farrukhabad is a city and parliamentary constituency in the Indian state of Uttar Pradesh, known historically for its trade and cultural significance.
  • 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_69c688143bfc81908d4176617735e601 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea39230481908401ead83d8666cd completed March 27, 2026, 8:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8275b07d08190a796f2b9884fcc33 completed March 28, 2026, 7:09 p.m.
Created at: March 27, 2026, 2:55 p.m.