Triple

T21208310
Position Surface form Disambiguated ID Type / Status
Subject Bishopric of Ösel–Wiek E522647 entity
Predicate hasNotableTown P14082 FINISHED
Object Lihula 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: Lihula | Statement: [Bishopric of Ösel–Wiek, hasNotableTown, Lihula]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lihula
Context triple: [Bishopric of Ösel–Wiek, hasNotableTown, Lihula]
  • A. Lihula chosen
    Lihula is a small historic town in western Estonia known for its medieval castle ruins and early role as a regional ecclesiastical and administrative center.
  • B. Kuusalu
    Kuusalu is a small borough in northern Estonia that serves as the main local hub for administration, services, and community life in the surrounding rural area.
  • C. Aruküla
    Aruküla is a small settlement in northern Estonia known for its rural character and proximity to Tallinn.
  • D. Kallaste
    Kallaste is a small Estonian town on the western shore of Lake Peipus, known for its Old Believer Russian community and distinctive sandstone cliffs.
  • E. Kivimäe
    Kivimäe is a residential subdistrict within the Nõmme district of Tallinn, Estonia, known for its green, suburban character.
  • 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_69e0b5112d8881909510b2dcdc93106d completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734362c788190bc1b96d3b84c0ad1 completed April 21, 2026, 8:24 a.m.
Created at: April 16, 2026, 3:25 p.m.