Triple

T15760350
Position Surface form Disambiguated ID Type / Status
Subject Trondenes Fort E382079 entity
Predicate locatedIn P40 FINISHED
Object Harstad 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: Harstad | Statement: [Trondenes Fort, locatedIn, Harstad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harstad
Context triple: [Trondenes Fort, locatedIn, Harstad]
  • A. Harstad
    Harstad is a coastal town and municipality in Troms county, known as an important regional center in Northern Norway with a strong maritime and cultural heritage.
  • B. Kristinestad
    Kristinestad is a small coastal town in western Finland known for its well-preserved wooden old town and historic maritime character.
  • C. Tonstad
    Tonstad is a small village in Agder county, Norway, serving as the administrative and commercial center of Sirdal municipality.
  • D. Harstad municipality chosen
    Harstad municipality is a local government area in Troms county, northern Norway, centered on the coastal town of Harstad and known for its maritime industries and Arctic landscape.
  • E. Stavern
    Stavern is a small coastal town in southern Norway known for its historic fortress, maritime heritage, and role as a popular summer holiday destination.
  • 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b52c548190a0ffa4493a4eb15c completed April 16, 2026, 3 a.m.
Created at: April 10, 2026, 4:47 a.m.