Triple

T12566682
Position Surface form Disambiguated ID Type / Status
Subject Greater Helsinki E295495 entity
Predicate contains P35 FINISHED
Object Loviisa E307202 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: Loviisa | Statement: [Greater Helsinki, contains, Loviisa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loviisa
Context triple: [Greater Helsinki, contains, Loviisa]
  • A. Loviisa chosen
    Loviisa is a small coastal town and municipality in southern Finland known for its historic wooden houses, seaside location, and nuclear power plant.
  • B. Ylivieska
    Ylivieska is a small town in Northern Ostrobothnia, Finland, known as a regional commercial and service center along the Kalajoki River.
  • C. Sotkamo
    Sotkamo is a municipality in eastern Finland known for its mining industry, outdoor recreation, and the popular Vuokatti ski and sports resort area.
  • D. Kirkee
    Kirkee is a cantonment town near Pune in Maharashtra, India, historically notable as the site of a major Anglo-Maratha War battle.
  • E. Imatra
    Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
  • 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_69ff90815b64819082715292f6088c74 completed May 9, 2026, 7:52 p.m.
Created at: April 8, 2026, 11:49 p.m.