Triple

T8592609
Position Surface form Disambiguated ID Type / Status
Subject Meilahti E203464 entity
Predicate adjacentTo P224 FINISHED
Object Munkkiniemi E220012 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: Munkkiniemi | Statement: [Meilahti, adjacentTo, Munkkiniemi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munkkiniemi
Context triple: [Meilahti, adjacentTo, Munkkiniemi]
  • A. Munkkiniemi chosen
    Munkkiniemi is a residential district in western Helsinki, Finland, known for its seaside location, parks, and notable architecture.
  • B. Kankaanpää
    Kankaanpää is a small town and municipality in the Satakunta region of western Finland, known for its surrounding forests and lakes.
  • C. Kirkkonummi
    Kirkkonummi is a municipality in southern Finland, located just west of Helsinki on the coast of the Gulf of Finland.
  • D. Matinkylä
    Matinkylä is a coastal residential and commercial district in the city of Espoo, Finland, known for its metro station and shopping center Iso Omena.
  • E. Rantasalmi
    Rantasalmi is a rural municipality in the Southern Savonia region of eastern Finland, known for its lakeside landscapes and traditional Finnish countryside.
  • 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_69cea8becbd88190837478e302d5e5b4 completed April 2, 2026, 5:34 p.m.
Created at: March 30, 2026, 6:23 p.m.