Triple
T35782103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianity in Anatolia |
E1034464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical religious phenomenon |
C14352
|
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: historical religious phenomenon Context triple: [Christianity in Anatolia, instanceOf, historical religious phenomenon]
-
A.
religious phenomenon
chosen
A religious phenomenon is any observable event, practice, experience, or pattern of belief that arises within or in relation to a religious tradition, worldview, or sense of the sacred.
-
B.
medieval religious movement
A medieval religious movement is a collective effort during the Middle Ages to reform, renew, or challenge existing religious beliefs and institutions, often blending spiritual, social, and political aims.
-
C.
historical religious community
A historical religious community is a group of people in a specific past time and place who shared common religious beliefs, practices, institutions, and identities that shaped their social and cultural life.
-
D.
historical religious institution
A historical religious institution is an organized body or establishment that has played a significant role in shaping and preserving religious beliefs, practices, and cultural traditions over an extended period in history.
-
E.
religious movement history
The religious movement history class examines the origins, development, key figures, beliefs, practices, and societal impacts of various religious movements across different historical periods and cultures.
- 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.