Triple

T8808880
Position Surface form Disambiguated ID Type / Status
Subject Nyland E209603 entity
Predicate containsCityHistorically P3786 FINISHED
Object Porvoo E305374 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: Porvoo | Statement: [Nyland, containsCityHistorically, Porvoo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Porvoo
Context triple: [Nyland, containsCityHistorically, Porvoo]
  • A. Porvoo chosen
    Porvoo is a historic coastal city in southern Finland known for its well-preserved wooden Old Town and medieval cathedral.
  • B. Pori
    Pori is a coastal city in western Finland known for its industrial heritage, port, and annual Pori Jazz Festival.
  • C. Lahti
    Lahti is a city in southern Finland known for its winter sports facilities, particularly ski jumping and cross-country skiing, and for hosting numerous international sporting events.
  • D. Lappeenranta
    Lappeenranta is a city in southeastern Finland near the Russian border, known for its lakeside location on Saimaa and its role as a regional commercial and educational center.
  • E. 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.
  • 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_69ca8363f3308190a47e3f1ebd51f613 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5fd4cbec8190a929d4e60da8ad65 completed March 31, 2026, 11:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69d316e50b548190b5f90a9753ad7cb0 completed April 6, 2026, 2:13 a.m.
Created at: March 30, 2026, 6:45 p.m.