Triple
T3756889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecclesiastical History |
E82069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church history |
C926
|
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 history Context triple: [Ecclesiastical History, instanceOf, church history]
-
A.
event in church history
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
B.
early Christian church
The early Christian church was the loosely organized community of Jesus’ followers in the first few centuries CE, developing its beliefs, practices, and leadership structures as it spread throughout the Roman Empire and beyond.
-
C.
Christian church
A Christian church is a community of believers in Jesus Christ who gather for worship, teaching, sacraments, fellowship, and service according to Christian faith and practice.
-
D.
history book
chosen
A history book is a written work that systematically records, analyzes, and interprets past events, societies, and developments to explain how they have shaped the present.
-
E.
historic church body
A historic church body is a long-established Christian denomination or ecclesiastical organization whose identity, structure, and traditions have been shaped over centuries of continuous institutional and theological development.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.