Triple

T21775236
Position Surface form Disambiguated ID Type / Status
Subject Ullensaker Church E537553 entity
Predicate ownedBy P347 FINISHED
Object Ullensaker parish 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: Ullensaker parish | Statement: [Ullensaker Church, ownedBy, Ullensaker parish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ullensaker parish
Context triple: [Ullensaker Church, ownedBy, Ullensaker parish]
  • A. Ullensaker chosen
    Ullensaker is a municipality in Viken county, Norway, best known for hosting Oslo Airport, Gardermoen, the country’s main international airport.
  • B. Fredrikstad parish
    Fredrikstad parish is a Church of Norway parish centered in the city of Fredrikstad, serving the local Lutheran congregation and community.
  • C. Oppstad parish
    Oppstad parish is a local Church of Norway parish serving the community within the municipality of Sør-Odal in Innlandet county.
  • D. Stovner district
    Stovner district is a residential borough in the northeastern part of Oslo, Norway, known for its diverse population and large housing estates.
  • E. Sagene district
    Sagene district is a central borough of Oslo, Norway, known for its historic industrial areas, riverside parks, and vibrant urban neighborhoods.
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f04627bd488190bbc1fde8db417b55 completed April 28, 2026, 5:31 a.m.
Created at: April 16, 2026, 6:51 p.m.