Triple
T2283294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannine community |
E51328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hypothetical 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: hypothetical early Christian community Context triple: [Johannine community, instanceOf, hypothetical 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 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.
-
C.
group of Christian hermits
A group of Christian hermits is a loosely associated community of individuals who live in solitude for religious devotion while sharing a common Christian faith, spiritual practices, and often mutual support or guidance.
-
D.
group of Christian monks
A group of Christian monks is a community of men who live together under religious vows, dedicating their lives to prayer, contemplation, and communal service according to a shared monastic rule.
-
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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:48 p.m.