Triple
T22679598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiiumaa Parish |
E560442
|
entity |
| Predicate | containsAdministrativeTerritorialEntity |
P747
|
FINISHED |
| Object | Kõrgessaare |
—
|
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: Kõrgessaare | Statement: [Hiiumaa Parish, containsAdministrativeTerritorialEntity, Kõrgessaare]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kõrgessaare Context triple: [Hiiumaa Parish, containsAdministrativeTerritorialEntity, Kõrgessaare]
-
A.
Kõrgessaare
chosen
Kõrgessaare is a small settlement on the island of Hiiumaa in western Estonia, known for its coastal location and rural character.
-
B.
Kuressaare
Kuressaare is the main town on Estonia’s Saaremaa island, known for its well-preserved medieval castle and seaside spa resort atmosphere.
-
C.
Raikküla
Raikküla is a village in central Estonia known for its rural landscape and historical manor, located within Rapla County.
-
D.
Aruküla
Aruküla is a small settlement in northern Estonia known for its rural character and proximity to Tallinn.
-
E.
Mäeküla
Mäeküla is a small settlement located in Järva County in central Estonia.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785f68b4819082c5570f741f5135 |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 3:11 p.m.