Triple

T13815445
Position Surface form Disambiguated ID Type / Status
Subject Helsinki region E332002 entity
Predicate contains P35 FINISHED
Object Raasepori E901750 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: Raasepori | Statement: [Helsinki region, contains, Raasepori]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raasepori
Context triple: [Helsinki region, contains, Raasepori]
  • A. Raasepori chosen
    Raasepori is a coastal town and municipality in southern Finland known for its medieval castle ruins and historic wooden town of Ekenäs.
  • B. Munkkiniemi
    Munkkiniemi is a residential district in western Helsinki, Finland, known for its seaside location, parks, and notable architecture.
  • C. Säynätsalo
    Säynätsalo is a former municipality in Central Finland, now part of the city of Jyväskylä, known especially for hosting Alvar Aalto’s renowned Säynätsalo Town Hall.
  • D. Kankaanpää
    Kankaanpää is a small town and municipality in the Satakunta region of western Finland, known for its surrounding forests and lakes.
  • E. Leppävaara
    Leppävaara is a major urban district and transport hub in Espoo, Finland, known for its large shopping center Sello and extensive rail and bus connections.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02806e148190996f58934e66d7d8 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd6474da3081909be6b892ef8cc73e completed May 8, 2026, 4:20 a.m.
Created at: April 9, 2026, 10:12 p.m.