Triple

T5773769
Position Surface form Disambiguated ID Type / Status
Subject Kuressaare E127388 entity
Predicate hasNameInLanguage P15 FINISHED
Object Kuressaare@et E127388 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: Kuressaare@et | Statement: [Kuressaare, hasNameInLanguage, Kuressaare@et]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuressaare@et
Context triple: [Kuressaare, hasNameInLanguage, Kuressaare@et]
  • A. Kuressaare chosen
    Kuressaare is the main town on Estonia’s Saaremaa island, known for its well-preserved medieval castle and seaside spa resort atmosphere.
  • B. 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.
  • C. Pääsküla
    Pääsküla is a subdistrict of the Nõmme district in Tallinn, Estonia, known for its residential areas and nearby natural landscapes.
  • D. Järveotsa
    Järveotsa is a residential subdistrict of the Mustamäe district in Tallinn, Estonia.
  • E. Pärnamäe
    Pärnamäe is a village located in Viimsi Parish in northern Estonia, near the capital city Tallinn.
  • 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_69c008361fa88190aefa4dc41b051e7f completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029af681081908276e99c568561ce completed March 22, 2026, 5:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69c07e6bf6348190b0ba46253585c7d9 completed March 22, 2026, 11:42 p.m.
Created at: March 22, 2026, 3:50 p.m.