Triple
T21208030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaarma municipality |
E522639
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Kirikuküla |
—
|
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: Kirikuküla | Statement: [Kaarma municipality, containsSettlement, Kirikuküla]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kirikuküla Context triple: [Kaarma municipality, containsSettlement, Kirikuküla]
-
A.
Aruküla
Aruküla is a small settlement in northern Estonia known for its rural character and proximity to Tallinn.
-
B.
Kaarma-Kirikuküla
chosen
Kaarma-Kirikuküla is a small village in Saare County on the island of Saaremaa in western Estonia.
-
C.
Raikküla
Raikküla is a village in central Estonia known for its rural landscape and historical manor, located within Rapla County.
-
D.
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.
-
E.
Veskiküla
Veskiküla is a small village located in Lääne-Harju Parish in northern 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734362c788190bc1b96d3b84c0ad1 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 3:25 p.m.