Triple
T5225441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clemens Romanus |
E117973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 1st-century Christian leader |
C17854
|
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: 1st-century Christian leader Context triple: [Clemens Romanus, instanceOf, 1st-century Christian leader]
-
A.
4th-century Christian bishop
A 4th-century Christian bishop was a high-ranking church leader responsible for overseeing a Christian community, defending orthodoxy amid theological controversies, and guiding the church through the transition from persecution to imperial favor.
-
B.
Protestant leader
A Protestant leader is an influential figure within Protestant Christianity who guides, teaches, and organizes believers according to Protestant doctrines and practices.
-
C.
founder of Christianity
The founder of Christianity is Jesus of Nazareth, whose life, teachings, death, and reported resurrection form the basis of the Christian faith and its global religious movement.
-
D.
6th-century Christian clergy
6th-century Christian clergy were ordained religious leaders who administered sacraments, guided spiritual life, and often wielded significant social and political influence within the early medieval Christian Church.
-
E.
Syriac Christian bishop
A Syriac Christian bishop is a high-ranking cleric within the Syriac Christian traditions who oversees dioceses, administers sacraments, preserves Syriac liturgical and theological heritage, and provides spiritual and administrative leadership to clergy and laity.
- F. None of above. chosen
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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:48 p.m.