Triple

T20823935
Position Surface form Disambiguated ID Type / Status
Subject Østerlars E512645 entity
Predicate partOf P40 FINISHED
Object Østerlars 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: Østerlars Parish | Statement: [Østerlars, partOf, Østerlars Parish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Østerlars Parish
Context triple: [Østerlars, partOf, Østerlars Parish]
  • A. Østerlars Parish chosen
    Østerlars Parish is an ecclesiastical and administrative parish on the Danish island of Bornholm, centered around the historic round church of Østerlars.
  • B. Bagsværd Parish
    Bagsværd Parish is a Church of Denmark parish in the suburb of Bagsværd near Copenhagen, serving the local Lutheran congregation and community.
  • C. Sund parish
    Sund parish is a local ecclesiastical and historical administrative district associated with Sund municipality in Norway.
  • D. Svene parish
    Svene parish is a local ecclesiastical and historical administrative area within the municipality of Flesberg in Norway.
  • E. Tretten parish
    Tretten parish is a Church of Norway parish serving the village of Tretten and surrounding areas in Øyer municipality in Innlandet county, Norway.
  • 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2fc0cd081909e264cda686579ea completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:41 p.m.