Triple
T22402222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhu |
E553788
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Muhu Parish |
—
|
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: Muhu Parish | Statement: [Muhu, partOf, Muhu Parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muhu Parish Context triple: [Muhu, partOf, Muhu Parish]
-
A.
Muhu Parish
chosen
Muhu Parish is a rural municipality in Saare County, Estonia, encompassing Muhu Island and several smaller surrounding islets.
-
B.
Vasalemma Parish
Vasalemma Parish was a former rural municipality in northern Estonia that was later incorporated into the larger Lääne-Harju Parish.
-
C.
Leisi Parish
Leisi Parish was a former rural municipality in Saare County, Estonia, known for its small villages and coastal landscapes before being merged into Saaremaa Parish.
-
D.
Kuusalu Parish
Kuusalu Parish is a rural municipality in northern Estonia known for its coastal landscapes, forests, and cultural heritage within Harju County.
-
E.
Saku Parish
Saku Parish is a rural municipality in northern Estonia known for its proximity to Tallinn and its mix of small-town communities, forests, and agricultural areas.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b4a96c8190838f5dda21c4d853 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 16, 2026, 8:46 p.m.