Triple

T33732504
Position Surface form Disambiguated ID Type / Status
Subject Münster im Elsass E864308 entity
Predicate hatReligiösenUrsprung P22741 FINISHED
Object Klostergründung 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: Klostergründung | Statement: [Münster im Elsass, hatReligiösenUrsprung, Klostergründung]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hatReligiösenUrsprung
Context triple: [Münster im Elsass, hatReligiösenUrsprung, Klostergründung]
  • A. hasReligiousOrigin chosen
    Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
  • B. ethnicReligion
    Indicates that a religion is closely associated with a particular ethnic group, often tied to that group’s culture, ancestry, or identity.
  • C. hasReligious
    Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
  • D. ethnicReligionVariant
    Indicates that one religion is a variant, branch, or localized form of another religion associated with a particular ethnic or cultural group.
  • E. religionAtOrigin
    Indicates that an entity had a particular religion or religious affiliation at the time or place of its origin.
  • 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_69f3498a64cc8190b4b414c67b280d93 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:44 a.m.