Triple
T11916177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Convocation area |
E283526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church administrative unit |
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: church administrative unit Context triple: [Charlotte Convocation area, instanceOf, church administrative unit]
-
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.
Kirchliches Gremium
Ein kirchliches Gremium ist eine organisierte Gruppe von Personen innerhalb einer Kirche, die gemeinsam Entscheidungen trifft, Beratungsaufgaben wahrnimmt oder bestimmte Verantwortungsbereiche in der kirchlichen Leitung und Verwaltung ausübt.
-
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.
court church
A court church is a Christian place of worship that is directly associated with and often located near a royal or princely court, serving the spiritual needs and ceremonial functions of the ruling household.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.