Triple

T21497621
Position Surface form Disambiguated ID Type / Status
Subject Synod of the Northeast E530395 entity
Predicate instanceOf P0 FINISHED
Object Presbyterian Church (U.S.A.) synod C37569 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: Presbyterian Church (U.S.A.) synod
Context triple: [Synod of the Northeast, instanceOf, Presbyterian Church (U.S.A.) synod]
  • A. Reformed synod
    A Reformed synod is an official governing assembly of ministers and elders within Reformed churches that meets to deliberate, decide, and provide oversight on doctrinal, disciplinary, and organizational matters.
  • B. Presbyterian church
    A Presbyterian church is a Christian congregation organized under a representative form of governance by elders, emphasizing Reformed theology, preaching, sacraments, and communal worship.
  • C. Presbyterian organization chosen
    A Presbyterian organization is a structured body within the Reformed Christian tradition that operates under Presbyterian governance, typically overseen by elected elders and organized into councils such as sessions, presbyteries, synods, and a general assembly.
  • D. conference of the United Church of Christ
    A conference of the United Church of Christ is a regional body that provides governance, support, and coordination for the denomination’s local congregations within a defined geographic area.
  • E. governing body of the Church of Scotland
    The governing body of the Church of Scotland is the General Assembly, a representative council of ministers, elders, and other members that meets to make decisions on doctrine, policy, and administration for the national church.
  • 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_69e0c45bd15481909fba5910765cdda2 completed April 16, 2026, 11:13 a.m.
Created at: April 16, 2026, 6:23 p.m.