Triple
T8592666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamminiemi |
E203465
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Seurasaari |
E752785
|
NE FINISHED |
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: Seurasaari | Statement: [Tamminiemi, near, Seurasaari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seurasaari Context triple: [Tamminiemi, near, Seurasaari]
-
A.
Seurasaari
chosen
Seurasaari is an island in Helsinki, Finland, best known for its open-air museum showcasing traditional Finnish wooden buildings and rural life.
-
B.
Suursaari
Suursaari is a large, strategically located island in the eastern Gulf of Finland, known for its rugged terrain, historical military significance, and shifting control between Finland and Russia.
-
C.
Siltasaari
Siltasaari is a central district of Helsinki, Finland, known for its urban waterfront setting and role as a key traffic and commercial hub.
-
D.
Lauttasaari
Lauttasaari is an island district of Helsinki, Finland, known for its residential areas, seaside parks, and easy access to the city center.
-
E.
Kemiönsaari
Kemiönsaari is a bilingual Finnish municipality and island community known for its coastal archipelago landscapes in Southwest Finland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4668b49481908838579e9876c1ec |
completed | March 31, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf425243d8819084af0a789c73ea7c |
completed | April 3, 2026, 4:30 a.m. |
Created at: March 30, 2026, 6:23 p.m.