Triple
T6458748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | church in Antioch |
E142061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Christian community |
C5821
|
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: early Christian community Context triple: [church in Antioch, instanceOf, early Christian community]
-
A.
early Christian church
chosen
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.
-
B.
early Christian work
An early Christian work is a text or artifact produced by followers of Jesus in the first centuries CE that expresses, develops, or transmits emerging Christian beliefs, practices, and community life.
-
C.
early Christian disciple
An early Christian disciple is a follower of Jesus in the first generations of the Christian movement who embraced his teachings, participated in the emerging church community, and helped spread the new faith.
-
D.
Late Antique Christian
A Late Antique Christian is an adherent of Christianity living between roughly the 3rd and 8th centuries CE, shaped by the Roman Empire’s transformation, emerging Christian institutions, and evolving theological and cultural debates.
-
E.
2nd-century Christian
A 2nd-century Christian is a follower of Jesus within the diverse and developing early Church of the 100s CE, navigating emerging doctrines, sporadic persecution, and the transition from apostolic tradition to organized theology and community life.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:48 p.m.