Triple

T1916071
Position Surface form Disambiguated ID Type / Status
Subject Bundelkhand E40019 entity
Predicate hasCity P316 FINISHED
Object Datia E110279 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: Datia | Statement: [Bundelkhand, hasCity, Datia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Datia
Context triple: [Bundelkhand, hasCity, Datia]
  • A. Datia chosen
    Datia is a historic town and administrative center in central India, known for its palaces and temples, located in the state of Madhya Pradesh.
  • B. Temeswar
    Temeswar (Timișoara) is a major city in western Romania known for its multicultural heritage and role in the 1989 Romanian Revolution.
  • C. Dewas
    Dewas is an industrial and commercial city in central India known for its manufacturing units, temples, and location along major transport routes in Madhya Pradesh.
  • D. Baniata
    Baniata is an Oceanic language of the Meso-Melanesian group spoken in the Solomon Islands.
  • E. Dehu
    Dehu is a pilgrimage town in Maharashtra, India, revered as the birthplace and spiritual center of the 17th-century Marathi saint-poet Tukaram.
  • 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_69a8864298748190a2f2fd34f7ef8d77 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb1e517e8819086e4bf5a305aeb25 completed March 7, 2026, 5:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69adf3da81308190a49844a8ac2997da completed March 8, 2026, 10:10 p.m.
Created at: March 4, 2026, 7:35 p.m.