Triple
T19582445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harku rural municipality |
E490028
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Rannamõisa |
—
|
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: Rannamõisa | Statement: [Harku rural municipality, hasSettlement, Rannamõisa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rannamõisa Context triple: [Harku rural municipality, hasSettlement, Rannamõisa]
-
A.
Rannamõisa
chosen
Rannamõisa is a village in northern Estonia known for its coastal location on the Baltic Sea and proximity to the capital, Tallinn.
-
B.
Tammneeme
Tammneeme is a coastal village in northern Estonia known for its seaside location on the Viimsi Peninsula near Tallinn.
-
C.
Õismäe
Õismäe is a residential subdistrict of Tallinn, Estonia, known for its large Soviet-era apartment blocks and distinctive circular street layout.
-
D.
Heltermaa
Heltermaa is a small port village on the eastern coast of Hiiumaa Island in Estonia, serving as a key ferry connection to the mainland.
-
E.
Mustjõe
Mustjõe is a subdistrict of Tallinn, Estonia, located within the Haabersti district.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404e18f88190b7fec59499dd25e8 |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.