Triple

T21208259
Position Surface form Disambiguated ID Type / Status
Subject Ösel–Wiek Diocese E522646 entity
Predicate seatMovedTo P39233 FINISHED
Object Haapsalu 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: Haapsalu | Statement: [Ösel–Wiek Diocese, seatMovedTo, Haapsalu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haapsalu
Context triple: [Ösel–Wiek Diocese, seatMovedTo, Haapsalu]
  • A. Haapsalu chosen
    Haapsalu is a small seaside town in western Estonia known for its historic wooden architecture, medieval castle, and traditional seaside resort and spa culture.
  • B. Rakvere
    Rakvere is a historic town in northern Estonia known for its medieval castle ruins and role as a regional cultural and economic center.
  • C. Võru
    Võru is a small town in southeastern Estonia known for its lakeside setting, traditional Võro culture, and role as a regional administrative and cultural center.
  • D. Jõhvi
    Jõhvi is a town in northeastern Estonia that serves as the administrative center of Ida-Viru County.
  • E. Kohtla-Järve
    Kohtla-Järve is an industrial city in northeastern Estonia known for its oil shale industry and diverse population.
  • 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.