Triple

T12566671
Position Surface form Disambiguated ID Type / Status
Subject Greater Helsinki E295495 entity
Predicate contains P35 FINISHED
Object Mäntsälä E845324 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: Mäntsälä | Statement: [Greater Helsinki, contains, Mäntsälä]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mäntsälä
Context triple: [Greater Helsinki, contains, Mäntsälä]
  • A. Mäntsälä chosen
    Mäntsälä is a municipality in southern Finland, located in the Uusimaa region and known for its rural character and proximity to the Helsinki metropolitan area.
  • B. Mummela
    Mummela is the traditional troupe of performers in the South Indian folk theatre form Yakshagana, responsible for enacting its mythological dance-drama narratives.
  • C. Imatra
    Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
  • D. Lempäälä
    Lempäälä is a municipality in the Pirkanmaa region of southern Finland, known for its lakeside landscapes and proximity to the city of Tampere.
  • E. Kerava
    Kerava is a small city in southern Finland known as a commuter town within the Greater Helsinki region.
  • 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_69d6ad9cac2c81908e8a7bed82d1e21d completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9549611c081909e611756f3cce7f0 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff82dcec0c8190a5e4ac0aafd34504 completed May 9, 2026, 6:54 p.m.
Created at: April 8, 2026, 11:49 p.m.