Triple
T38374188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advent Christian Church |
E893572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Adventist denomination |
C350
|
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: Adventist denomination Context triple: [Advent Christian Church, instanceOf, Adventist denomination]
-
A.
Seventh-day Adventist organization
A Seventh-day Adventist organization is an entity formally affiliated with the Seventh-day Adventist Church that advances its religious, educational, health, or humanitarian mission in harmony with Adventist beliefs and governance.
-
B.
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.
-
C.
Universalist denomination
A Universalist denomination is a religious organization or tradition that emphasizes the belief in universal salvation or the ultimate reconciliation of all souls with the divine.
-
D.
Christian denomination
chosen
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.
-
E.
Seventh-day Adventist college
A Seventh-day Adventist college is a higher education institution that integrates academic programs with the beliefs, values, and lifestyle principles of the Seventh-day Adventist 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.