Triple

T6734876
Position Surface form Disambiguated ID Type / Status
Subject Orchha E153727 entity
Predicate wasCapitalOf P3417 FINISHED
Object Orchha State E518185 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: Orchha State | Statement: [Orchha, wasCapitalOf, Orchha State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orchha State
Context triple: [Orchha, wasCapitalOf, Orchha State]
  • A. Orchha State chosen
    Orchha State was a princely state in central India, historically ruled by the Bundela Rajputs with its capital at the town of Orchha, known for its palaces and temples.
  • B. Chhatarpur State
    Chhatarpur State was a princely state in British India, located in the Bundelkhand region and ruled by a local dynasty under British suzerainty.
  • C. Rajgarh State
    Rajgarh State was a former princely state in central India that existed under British suzerainty until Indian independence.
  • D. Ajaigarh State
    Ajaigarh State was a former princely state in British India, located in what is now central India and ruled by a local dynasty under indirect colonial administration.
  • E. Dholpur State
    Dholpur State was a princely state in northern India, ruled by Jat rulers and located in the region that is now part of Rajasthan.
  • 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_69c6880bdd68819097de8b6099992682 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d16ecbe08190b019d547f631a725 completed March 27, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c70b0703288190906cfcaba9d9c85a completed March 27, 2026, 10:56 p.m.
Created at: March 27, 2026, 2:09 p.m.