Triple

T20456521
Position Surface form Disambiguated ID Type / Status
Subject Eidskog E501802 entity
Predicate bordersWith P224 FINISHED
Object Kongsvinger NE NERFINISHED

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: Kongsvinger | Statement: [Eidskog, bordersWith, Kongsvinger]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kongsvinger
Context triple: [Eidskog, bordersWith, Kongsvinger]
  • A. Kongsvinger chosen
    Kongsvinger is a town and municipality in Innlandet county, Norway, known for its historic fortress overlooking the Glomma River and its role as a regional center near the Swedish border.
  • B. Høyanger
    Høyanger is a small industrial village and municipality in Vestland county, western Norway, known for its hydropower-based aluminum production and dramatic fjord landscape.
  • C. 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.
  • D. Kvænangen
    Kvænangen is a fjord in northern Norway known for its dramatic coastal scenery, rich marine life, and traditional fishing communities.
  • E. Ringerike
    Ringerike is a historic district and municipality in southeastern Norway known for its rich Viking-age heritage and distinctive cultural traditions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4ad4940819098cf2ff6413574e5 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e696a1b03c8190984d9db6d3251308 completed April 20, 2026, 9:12 p.m.
Created at: April 16, 2026, 11:32 a.m.