Triple
T19581893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siili |
E490012
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdistrict of Tallinn |
C16915
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: subdistrict of Tallinn Context triple: [Siili, instanceOf, subdistrict of Tallinn]
-
A.
district of Tallinn
chosen
A district of Tallinn is an administrative subdivision of Estonia’s capital city that encompasses specific neighborhoods and local governance functions within the municipal structure.
-
B.
district of Helsinki
A district of Helsinki is an administrative and geographical subdivision of Finland’s capital city, defined for governance, planning, and statistical purposes, typically comprising several neighborhoods with shared services and infrastructure.
-
C.
district of Espoo
A district of Espoo is an administrative and geographical subdivision of the city of Espoo, Finland, defined for local governance, planning, and statistical purposes.
-
D.
district of Kaliningrad
A district of Kaliningrad is an administrative subdivision within the city of Kaliningrad, Russia, responsible for local governance, public services, and community infrastructure in its designated urban area.
-
E.
district of Reykjavík
A district of Reykjavík is an administrative and geographical subdivision of Iceland’s capital city, encompassing specific neighborhoods, services, and local governance functions within its defined area.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 10, 2026, 1:42 p.m.