Triple

T22714055
Position Surface form Disambiguated ID Type / Status
Subject Leisi E561678 entity
Predicate locatedIn P40 FINISHED
Object Saaremaa Parish 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: Saaremaa Parish | Statement: [Leisi, locatedIn, Saaremaa Parish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saaremaa Parish
Context triple: [Leisi, locatedIn, Saaremaa Parish]
  • A. Saaremaa Parish chosen
    Saaremaa Parish is a rural municipality in western Estonia that encompasses much of Saaremaa Island, including the historic town of Kuressaare and its medieval castle.
  • B. Hiiumaa Parish
    Hiiumaa Parish is a rural municipality in Hiiu County, Estonia, encompassing much of the island of Hiiumaa and its settlements.
  • C. Tapa Parish
    Tapa Parish is a rural municipality in northern Estonia known for its central town of Tapa and its role as a local administrative and transport hub within Lääne-Viru County.
  • D. Peipsiääre Parish
    Peipsiääre Parish is a rural municipality in eastern Estonia situated along the shores of Lake Peipus in Tartu County.
  • E. Kuusalu Parish
    Kuusalu Parish is a rural municipality in northern Estonia known for its coastal landscapes, forests, and cultural heritage within Harju County.
  • 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_69e2454f1348819088d83f420925a5c1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1790bdac88190976c83c9039c9d16 completed April 29, 2026, 3:20 a.m.
Created at: April 17, 2026, 3:18 p.m.