Triple

T16903739
Position Surface form Disambiguated ID Type / Status
Subject Sør-Varanger E424503 entity
Predicate bordersMunicipality P224 FINISHED
Object Nesseby E1022319 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: Nesseby | Statement: [Sør-Varanger, bordersMunicipality, Nesseby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nesseby
Context triple: [Sør-Varanger, bordersMunicipality, Nesseby]
  • A. Nesseby chosen
    Nesseby is a small coastal municipality in Troms og Finnmark county in northern Norway, known for its Sámi culture and location along the Varangerfjorden.
  • B. Nesbyen
    Nesbyen is a small town and municipality in southeastern Norway known for its inland valley setting, historic wooden buildings, and notably warm summer temperatures.
  • C. Keadby
    Keadby is a village in North Lincolnshire, England, known for its location on the River Trent and its nearby power station and transport links.
  • D. Nockeby
    Nockeby is a residential district in western Stockholm, Sweden, known as the terminus of one of the city's historic tram lines.
  • E. Edsbyn
    Edsbyn is a small town in Gävleborg County, Sweden, known for its bandy team and role as a local industrial and service center.
  • 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_69d889da3e8c8190a2b118f383f0beac completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3c8de3070819085bfe9696bc887ea completed April 18, 2026, 6:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c7b47a6081909d8609c2bce96d1a completed May 10, 2026, 6 p.m.
Created at: April 10, 2026, 5:30 a.m.