Triple
T9693304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelism Department |
E234587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | department of a Christian denomination |
C16072
|
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: department of a Christian denomination Context triple: [Evangelism Department, instanceOf, department of a Christian denomination]
-
A.
administrative unit of the Seventh-day Adventist Church
An administrative unit of the Seventh-day Adventist Church is an organizational entity, such as a conference, mission, union, or division, responsible for overseeing and coordinating the church’s activities, governance, and ministries within a defined geographic territory.
-
B.
church organization
chosen
A church organization is a structured religious entity that coordinates worship, spiritual leadership, community services, and administrative functions for a specific faith community.
-
C.
religious denomination
A religious denomination is a distinct subgroup within a larger religious tradition, characterized by shared doctrines, practices, organizational structures, and identity.
-
D.
ecclesiastical institution
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
-
E.
Christian denomination
A Christian denomination is an organized branch within Christianity that shares a distinct set of doctrines, practices, governance structures, and traditions while affirming core Christian beliefs.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:17 p.m.