Triple

T2194615
Position Surface form Disambiguated ID Type / Status
Subject Shah Alam II E49941 entity
Predicate alliedWith P37 FINISHED
Object Mir Qasim E175462 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: Mir Qasim | Statement: [Shah Alam II, alliedWith, Mir Qasim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mir Qasim
Context triple: [Shah Alam II, alliedWith, Mir Qasim]
  • A. Mir Qasim chosen
    Mir Qasim was the Nawab of Bengal in the mid-18th century, known for his resistance to British expansion in India and his defeat in the Battle of Buxar in 1764.
  • B. Thadiq
    Thadiq is a town in central Saudi Arabia known for its traditional architecture and location within the Riyadh administrative region.
  • C. Khudayar Khan
    Khudayar Khan was a 19th-century ruler of the Kokand Khanate in Central Asia, known for his turbulent reign marked by internal strife and increasing Russian influence in the region.
  • D. Khurram
    Khurram, better known as the Mughal emperor Shah Jahan, was the ruler of the Mughal Empire famed for commissioning the Taj Mahal.
  • E. Omar Khan
    Omar Khan was a prominent 19th-century ruler of the Kokand Khanate in Central Asia, known for his patronage of culture and literature.
  • 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_69a88aaba3c48190b351cab9b26989ff completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abbf74147c81908793c3694894f94a completed March 7, 2026, 6:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae65427de48190be3dbc9c0a888332 completed March 9, 2026, 6:14 a.m.
Created at: March 4, 2026, 7:46 p.m.