Triple

T20442655
Position Surface form Disambiguated ID Type / Status
Subject Heddal Stave Church E501433 entity
Predicate hasNearbyCity P350 FINISHED
Object Notodden 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: Notodden | Statement: [Heddal Stave Church, hasNearbyCity, Notodden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Notodden
Context triple: [Heddal Stave Church, hasNearbyCity, Notodden]
  • A. Notodden chosen
    Notodden is a town and municipality in Vestfold og Telemark county, Norway, known for its industrial heritage and annual blues festival.
  • B. Ofoten
    Ofoten is a district in Nordland county in northern Norway, known for its fjords, mountains, and the port town of Narvik.
  • C. Trysil
    Trysil is a Norwegian municipality renowned for its large alpine ski resort and extensive outdoor recreation opportunities.
  • D. 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.
  • E. Bjerkreim
    Bjerkreim is a rural municipality in southwestern Norway known for its rivers, salmon fishing, and agricultural landscape.
  • 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_69e0b4ac0a1c81908845d0f8a56abce8 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e685f3b794819080745b135a305ba7 completed April 20, 2026, 8 p.m.
Created at: April 16, 2026, 11:32 a.m.