Triple

T1088593
Position Surface form Disambiguated ID Type / Status
Subject Saaremaa E24108 entity
Predicate contains P35 FINISHED
Object Saaremaa municipality E24108 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: Saaremaa municipality | Statement: [Saaremaa, contains, Saaremaa municipality]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saaremaa municipality
Context triple: [Saaremaa, contains, Saaremaa municipality]
  • A. Kuressaare
    Kuressaare is the main town on Estonia’s Saaremaa island, known for its well-preserved medieval castle and seaside spa resort atmosphere.
  • B. Harku Parish
    Harku Parish is a rural municipality in northern Estonia, located just west of the capital city Tallinn.
  • C. Saaremaa chosen
    Saaremaa is the largest island of Estonia, known for its rugged coastline, medieval Kuressaare Castle, and distinctive windmills and juniper landscapes.
  • D. Viimsi Parish
    Viimsi Parish is a suburban rural municipality in northern Estonia, located on the Viimsi Peninsula just northeast of the capital city Tallinn.
  • E. Nõmme
    Nõmme is a leafy, villa-filled suburban district of Tallinn known for its pine forests, wooden architecture, and small-town atmosphere within the capital.
  • 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_69a49404428c819092dcc9632f5f7b8b completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b97d85708190a1630256648aa4a2 completed March 1, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac599e543c8190bbb0558379d8d9d5 completed March 7, 2026, 5 p.m.
Created at: March 1, 2026, 7:42 p.m.