Triple

T18198371
Position Surface form Disambiguated ID Type / Status
Subject Nidarosdomen E435719 entity
Predicate locatedIn P40 FINISHED
Object Nidaros 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: Nidaros | Statement: [Nidarosdomen, locatedIn, Nidaros]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nidaros
Context triple: [Nidarosdomen, locatedIn, Nidaros]
  • A. Nidarosdomen
    Nidarosdomen is a historic Gothic cathedral in Trondheim, Norway, renowned as a national shrine and traditional coronation site for Norwegian monarchs.
  • B. Trondheim chosen
    Trondheim is a historic Norwegian city in Trøndelag county, known for its medieval Nidaros Cathedral and role as a former capital of Norway.
  • C. Bergen Cathedral
    Bergen Cathedral is a historic Lutheran church in Bergen, Norway, serving as the city’s main cathedral and seat of the bishop.
  • D. Stavanger Cathedral
    Stavanger Cathedral is a medieval stone church in Stavanger, Norway, and the country's oldest cathedral still in continuous use.
  • E. Oslo Cathedral
    Oslo Cathedral is the main church of the Church of Norway Diocese of Oslo, a historic Lutheran cathedral located in the center of Norway’s capital city.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d47f1c819082eec59492497797 completed April 19, 2026, 2:04 p.m.
Created at: April 10, 2026, 10:31 a.m.