Triple

T8677429
Position Surface form Disambiguated ID Type / Status
Subject Österbottens landskap E205950 entity
Predicate containsMunicipality P852 FINISHED
Object Nykarleby E215151 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: Nykarleby | Statement: [Österbottens landskap, containsMunicipality, Nykarleby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nykarleby
Context triple: [Österbottens landskap, containsMunicipality, Nykarleby]
  • A. Nykarleby chosen
    Nykarleby is a small bilingual coastal town and municipality in western Finland known for its Swedish-speaking majority and location in the Ostrobothnia region.
  • B. Bremsnes
    Bremsnes is a village on the island of Averøya in Møre og Romsdal county, Norway, known for its coastal setting and local church.
  • C. Bjerke
    Bjerke is a neighborhood in the Bjerke borough of Oslo, Norway, known primarily as a residential area with local services and amenities.
  • D. Stordal
    Stordal is a small village and former municipality in western Norway, known for its scenic fjord landscape and traditional Norwegian architecture.
  • E. Sandvika
    Sandvika is a town in southeastern Norway that serves as the administrative center of Bærum and a commercial hub in the Greater Oslo 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_69ca83529a9c8190b5c075b4f14636ed completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc49f7c2c081909ec93413ceefbb1c completed March 31, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf28748c0c8190a8870650a9b07d7d completed April 3, 2026, 2:39 a.m.
Created at: March 30, 2026, 6:32 p.m.