Triple

T4113689
Position Surface form Disambiguated ID Type / Status
Subject Turku E90238 entity
Predicate hasSwedishName P11737 FINISHED
Object Åbo 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: Åbo | Statement: [Turku, hasSwedishName, Åbo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Åbo
Context triple: [Turku, hasSwedishName, Åbo]
  • A. 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.
  • B. 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.
  • C. Jakobstad
    Jakobstad is a coastal town and municipality in western Finland known for its bilingual (Finnish and Swedish) heritage and maritime history.
  • D. Sundsvall
    Sundsvall is a coastal city in central Sweden known as an important industrial and commercial center on the Gulf of Bothnia.
  • E. Umeå
    Umeå is a university city in northern Sweden known for its cultural scene, research institutions, and role as a regional economic hub.
  • 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_69aed95c080881908125e30c5dcdc6f8 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af01e06ce48190b840d931e44095ea completed March 9, 2026, 5:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69b56b8e30448190a1ac0df969c83631 completed March 14, 2026, 2:07 p.m.
Created at: March 9, 2026, 3:41 p.m.