Triple

T19523272
Position Surface form Disambiguated ID Type / Status
Subject Vidzeme region E488456 entity
Predicate borders P224 FINISHED
Object Latgale region E154233 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: Latgale region | Statement: [Vidzeme region, borders, Latgale region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Latgale region
Context triple: [Vidzeme region, borders, Latgale region]
  • A. Latgale chosen
    Latgale is a culturally distinct historical region in eastern Latvia, known for its lakes, rolling landscapes, and strong Latgalian linguistic and Catholic traditions.
  • B. Zemgale
    Zemgale is a historical and cultural region in southern Latvia, known for its fertile plains and agricultural significance.
  • C. Ventspils District
    Ventspils District was a former administrative division in western Latvia, centered around the city and port of Ventspils in the historical region of Kurzeme.
  • D. Jetysu region
    Jetysu region is a historic area in southeastern Kazakhstan known as the ancestral homeland of several Kazakh clans and a key center of nomadic culture along the Silk Road.
  • E. Saldus District
    Saldus District was an administrative division in western Latvia, historically part of the Kurzeme (Courland) 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_69d8e8da8bec819081f400199491ccc3 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e636392444819094f6a2aa1cdf3d42 completed April 20, 2026, 2:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0771a1ebac819090982f36b4c02446 completed May 15, 2026, 7:18 p.m.
Created at: April 10, 2026, 1:41 p.m.