Triple

T9611350
Position Surface form Disambiguated ID Type / Status
Subject Erkki Tuomioja E232107 entity
Predicate workLocation P7 FINISHED
Object Helsinki E14163 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: Helsinki | Statement: [Erkki Tuomioja, workLocation, Helsinki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Helsinki
Context triple: [Erkki Tuomioja, workLocation, Helsinki]
  • A. Helsinki chosen
    Helsinki is the capital and largest city of Finland, known for its coastal location on the Baltic Sea, modern design, and vibrant cultural life.
  • B. Espoo
    Espoo is Finland’s second-largest city, located just west of Helsinki on the southern coast, known for its technology industry, natural landscapes, and role as part of the Helsinki metropolitan area.
  • C. Turku
    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.
  • D. Tampere
    Tampere is a major industrial and cultural city in southern Finland, historically significant as a key battleground in the Finnish Civil War.
  • E. Porvoo
    Porvoo is a historic coastal city in southern Finland known for its well-preserved wooden Old Town and medieval cathedral.
  • 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_69ca8485a90c819094fe40b42fde9d70 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a87764481909ab96cd2ab96d14b completed April 1, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69d2997e60b081908c4982db477de5a1 completed April 5, 2026, 5:18 p.m.
Created at: March 30, 2026, 8:09 p.m.