Triple

T4611447
Position Surface form Disambiguated ID Type / Status
Subject Birbal’s House E100565 entity
Predicate near P350 FINISHED
Object Diwan-i-Khas E69647 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: Diwan-i-Khas | Statement: [Birbal’s House, near, Diwan-i-Khas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Diwan-i-Khas
Context triple: [Birbal’s House, near, Diwan-i-Khas]
  • A. Diwan-i-Khas chosen
    Diwan-i-Khas is the ornate marble hall of private audience in Delhi’s Red Fort, where Mughal emperors once held exclusive court and state discussions.
  • B. Diwan-i-Khas
    Diwan-i-Khas is an ornate hall of private audience in Jaipur’s City Palace, renowned for its intricate Mughal-Rajput architecture and historic royal gatherings.
  • C. Diwan-i-Makhfi
    Diwan-i-Makhfi is a celebrated Persian poetry collection attributed to Mughal princess and poet Zeb-un-Nissa, showcasing her mystical and lyrical verse.
  • D. Diwan-i-Aam
    Diwan-i-Aam is the historic public audience hall within Jaipur’s City Palace complex, where the rulers once addressed and interacted with their subjects.
  • E. Diwan-i-Aam
    Diwan-i-Aam is the public audience hall in Delhi’s Red Fort where Mughal emperors historically met and addressed the general populace.
  • 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_69bd43cce1e08190a07d53af6a9b6c24 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd59bffbf08190b13ef0810e6f9d19 completed March 20, 2026, 2:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69be035629248190a8723b5f1f9e57bc completed March 21, 2026, 2:32 a.m.
Created at: March 20, 2026, 1:12 p.m.