Triple

T30824615
Position Surface form Disambiguated ID Type / Status
Subject Chapter of the Diocese of Lapua E785019 entity
Predicate instanceOf P0 FINISHED
Object administrative body of a Lutheran diocese C41566 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: administrative body of a Lutheran diocese
Context triple: [Chapter of the Diocese of Lapua, instanceOf, administrative body of a Lutheran diocese]
  • A. Lutheran diocese
    A Lutheran diocese is an administrative and ecclesiastical district of the Lutheran Church, overseen by a bishop and comprising multiple congregations within a defined geographic area.
  • B. governing body of an Eastern Catholic Church
    The governing body of an Eastern Catholic Church is the synodal or hierarchical authority—such as a synod of bishops or patriarchal/major archiepiscopal council—that exercises supreme legislative, administrative, and judicial power within that particular Church in full communion with the Pope.
  • C. denominational body
    A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
  • D. Lutheran church office
    A Lutheran church office is the administrative center of a Lutheran congregation where pastoral staff and lay workers coordinate worship, ministries, records, and daily church operations.
  • E. ecclesiastical office-holding body chosen
    An ecclesiastical office-holding body is a formally constituted group within a religious organization that collectively holds, administers, or oversees specific church offices, duties, or authorities.
  • F. None of above.

Provenance (1 batch)

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_69f224b6642481909e8d701de2cd1a53 completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:44 p.m.