Triple
T5989345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saare County |
E133304
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Kuressaare |
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 | Statement: [Saare County, hasSettlement, Kuressaare]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuressaare Context triple: [Saare County, hasSettlement, Kuressaare]
-
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.
Ruhnu
Ruhnu is a small Estonian island in the Gulf of Riga, known for its remote location, traditional wooden lighthouse and church, and unique cultural heritage.
-
C.
Naissaar
Naissaar is a forested Estonian island in the Baltic Sea known for its military history, nature reserves, and proximity to Tallinn.
-
D.
Saaremaa
Saaremaa is the largest island of Estonia, known for its rugged coastline, medieval Kuressaare Castle, and distinctive windmills and juniper landscapes.
-
E.
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.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc76fd481908cc3f327e532a1a6 |
completed | March 22, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e3a5d54c8190b2bc8b3291f8ac2f |
completed | March 27, 2026, 1:55 a.m. |
Created at: March 22, 2026, 4:04 p.m.