Triple

T7344602
Position Surface form Disambiguated ID Type / Status
Subject Jaunsari E169343 entity
Predicate glottologName P6521 FINISHED
Object Jaunsari E169343 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: Jaunsari | Statement: [Jaunsari, glottologName, Jaunsari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jaunsari
Context triple: [Jaunsari, glottologName, Jaunsari]
  • A. Jaunsari chosen
    Jaunsari is an Indo-Aryan language spoken by the Jaunsari people in the Jaunsar-Bawar region of northern India.
  • B. 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.
  • C. 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.
  • D. Kalnciems
    Kalnciems is a settlement in present-day Latvia historically associated with the Baltic German nobility, including the birth of Ernst Johann von Biron, Duke of Courland.
  • E. Varniai
    Varniai is a historic town in Lithuania that once served as a key political and religious center of the Samogitian region.
  • 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_69c68a57710481909f0c1f3c6ebdb6f2 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f0eeb30081909d25704ac9b49d0e completed March 27, 2026, 9:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802b24194819096b796de15d66ed2 completed March 28, 2026, 4:32 p.m.
Created at: March 27, 2026, 3:05 p.m.