Triple
T897093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianization of the Roman Empire |
E19368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious transformation |
C4112
|
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: religious transformation Context triple: [Christianization of the Roman Empire, instanceOf, religious transformation]
-
A.
religious conversion movement
chosen
A religious conversion movement is a collective effort or organized campaign aimed at persuading individuals or groups to adopt a new religious faith, denomination, or set of spiritual beliefs, often involving structured teachings, rituals, and community support.
-
B.
Christian reform movement
A Christian reform movement is a religious initiative within Christianity aimed at renewing faith, correcting perceived doctrinal or moral errors, and transforming church practices or social structures in light of biblical principles.
-
C.
religious belief
Religious belief is a deeply held conviction or faith in spiritual principles, deities, or transcendent realities that shapes an individual's understanding of existence, morality, and purpose.
-
D.
religious tradition
A religious tradition is an enduring, socially shared system of beliefs, practices, narratives, and institutions that shapes how a community understands and relates to the sacred, the moral order, and ultimate meaning.
-
E.
Christian convert
A Christian convert is a person who has adopted the Christian faith, typically after previously adhering to a different religion, belief system, or no religion at all.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.