Triple
T21720637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop Peter II of Ravenna |
E536145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late 5th-century religious leader |
C45202
|
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: late 5th-century religious leader Context triple: [Archbishop Peter II of Ravenna, instanceOf, late 5th-century religious leader]
-
A.
5th-century saint
A 5th-century saint is a revered Christian holy figure from the 400s CE, venerated for exemplary faith, virtue, and often associated with miracles or martyrdom within early Church tradition.
-
B.
1st-century Christian leader
A 1st-century Christian leader is an influential figure from the earliest decades of the Christian movement who guided communities, taught doctrine, and helped shape the faith’s foundational beliefs and practices.
-
C.
15th-century religious leader
A 15th-century religious leader is an influential spiritual authority who guided religious practice, doctrine, and community life within the sociopolitical and cultural context of the 1400s.
-
D.
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.
-
E.
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.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:47 p.m.