Triple

T8106911
Position Surface form Disambiguated ID Type / Status
Subject Archdiocese of Uppsala E189248 entity
Predicate hasPreReformationOrigin P41082 FINISHED
Object yes LITERAL FINISHED

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: yes | Statement: [Archdiocese of Uppsala, hasPreReformationOrigin, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPreReformationOrigin
Context triple: [Archdiocese of Uppsala, hasPreReformationOrigin, yes]
  • A. religionBeforeReformation chosen
    Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
  • B. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • C. laterReformedAs
    Indicates that an entity was subsequently reorganized, renamed, or transformed into another entity at a later time.
  • D. underwentReformation
    Indicates that an entity experienced a significant process of change, restructuring, or reform that altered its previous state or practices.
  • E. hasReligiousOrigin
    Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
  • F. None of above.

Provenance (3 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_69ca82b9d5848190a24672775d5c5011 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb42f89dd481908f1a25e4b16a8fc8 completed March 31, 2026, 3:43 a.m.
PD Predicate disambiguation batch_69cb04a2ed1c8190b73562321ad688bc completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:31 p.m.