Triple

T18132660
Position Surface form Disambiguated ID Type / Status
Subject Dehradun district E434051 entity
Predicate regionalLanguage P237 FINISHED
Object Jaunsari NE NERFINISHED

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: Jaunsari | Statement: [Dehradun district, regionalLanguage, Jaunsari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jaunsari
Context triple: [Dehradun district, regionalLanguage, Jaunsari]
  • A. Jaunsari chosen
    Jaunsari is an Indo-Aryan language spoken by the Jaunsari people in the Jaunsar-Bawar region of northern India.
  • B. Sakiai
    Sakiai is a small town in southwestern Lithuania known for its proximity to the Russian and Polish borders and its role as a local administrative and cultural center.
  • C. Jaunliepāja
    Jaunliepāja is a district of the Latvian port city of Liepāja, known for its mix of residential areas and industrial heritage near the Baltic Sea coast.
  • D. Cēsis
    Cēsis is a historic town in northern Latvia known for its medieval castle, well-preserved old town, and role in Latvian cultural and national history.
  • E. Rietavas
    Rietavas is a historic town in western Lithuania, known as one of the main centers of the Samogitian region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de04321c81909c0b9d47757720fd completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.