Triple
T4239235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Turku |
E94768
|
entity |
| Predicate | associatedWithCity |
P1481
|
FINISHED |
| Object | Turku |
E90238
|
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: Turku | Statement: [Diocese of Turku, associatedWithCity, Turku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Turku Context triple: [Diocese of Turku, associatedWithCity, Turku]
-
A.
Turku
chosen
Turku is one of Finland’s oldest and historically most important cities, located on the southwest coast and known for its medieval heritage and major Baltic Sea port.
-
B.
Tampere
Tampere is a major industrial and cultural city in southern Finland, historically significant as a key battleground in the Finnish Civil War.
-
C.
Porvoo
Porvoo is a historic coastal city in southern Finland known for its well-preserved wooden Old Town and medieval cathedral.
-
D.
Helsinki
Helsinki is the capital and largest city of Finland, known for its coastal location on the Baltic Sea, modern design, and vibrant cultural life.
-
E.
Vaasa
Vaasa is a coastal city in western Finland known for its maritime heritage, bilingual Finnish-Swedish culture, and role as a regional economic and educational center.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e76b6e0819084d0ce137b5ba74e |
completed | March 12, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be100f9e58819088fa92122cd57455 |
completed | March 21, 2026, 3:27 a.m. |
Created at: March 12, 2026, 11:05 p.m.