Triple
T35782105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianity in Anatolia |
E1034464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | history of Christianity by region |
C19452
|
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: history of Christianity by region Context triple: [Christianity in Anatolia, instanceOf, history of Christianity by region]
-
A.
history of Christianity
The history of Christianity is the study of the origins, development, beliefs, practices, institutions, and global impact of the Christian faith from its beginnings in the first century to the present day.
-
B.
Christianity by country
chosen
Christianity by country is a conceptual class that categorizes and compares nations based on the presence, distribution, and characteristics of Christian populations and traditions within their borders.
-
C.
historian of Christianity
A historian of Christianity is a scholar who researches, analyzes, and interprets the development, beliefs, practices, and institutions of Christian traditions across different historical periods and cultural contexts.
-
D.
era of Christian history
An era of Christian history is a distinct period characterized by particular theological developments, ecclesiastical structures, cultural influences, and historical events that shape the life and thought of the Christian church.
-
E.
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.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.