Triple

T17516389
Position Surface form Disambiguated ID Type / Status
Subject Semigallia E426578 entity
Predicate majorCity P316 FINISHED
Object Jēkabpils 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: Jēkabpils | Statement: [Semigallia, majorCity, Jēkabpils]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jēkabpils
Context triple: [Semigallia, majorCity, Jēkabpils]
  • A. Jekabpils chosen
    Jekabpils is a town in southeastern Latvia known for its historic architecture and scenic location along the Daugava River.
  • B. Kuldīga
    Kuldīga is a historic town in western Latvia known for its well-preserved old town and proximity to the Venta Rapid, one of Europe’s widest natural waterfalls.
  • C. Jelgava
    Jelgava is a city in central Latvia known for its historic Jelgava Palace and role as a regional cultural and educational center.
  • D. Bauska
    Bauska is a historic town in southern Latvia known for its medieval castle and location at the confluence of the Mūsa and Mēmele rivers, which form the Lielupe.
  • E. Rēzekne
    Rēzekne is a city in eastern Latvia that serves as one of the main cultural, economic, and transportation centers of the Latgale 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_69d889dd9164819087b1dc3c9240c870 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4526097388190ba1a949064962a24 completed April 19, 2026, 3:56 a.m.
Created at: April 10, 2026, 5:49 a.m.