Triple

T12846949
Position Surface form Disambiguated ID Type / Status
Subject Loviisa Nuclear Power Plant E307202 entity
Predicate locatedIn P40 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: [Loviisa Nuclear Power Plant, locatedIn, Loviisa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loviisa
Context triple: [Loviisa Nuclear Power Plant, locatedIn, 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96ff49efc8190bd6bbac510cc4705 completed April 10, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a007d960bd08190b8ac366273646865 completed May 10, 2026, 12:44 p.m.
Created at: April 9, 2026, 5:36 p.m.