Triple
T7167393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Siricius |
E167105
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 4th-century pope |
C4610
|
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: 4th-century pope Context triple: [Pope Siricius, instanceOf, 4th-century pope]
-
A.
4th-century Christian bishop
chosen
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.
5th-century Italian bishop
A 5th-century Italian bishop was a high-ranking Christian cleric in Italy responsible for overseeing a diocese, guiding religious practice, and engaging in theological and political affairs during the late Roman and early post-Roman period.
-
C.
4th-century Roman emperor
A 4th-century Roman emperor is a sovereign ruler of the Roman Empire during the 300s CE, navigating military, religious, and administrative transformations that reshaped the ancient Mediterranean world.
-
D.
3rd-century Christian bishop
A 3rd-century Christian bishop was a regional church leader responsible for overseeing Christian communities, doctrine, and worship during a period of persecution and theological development in the Roman Empire.
-
E.
4th-century Roman person
A 4th-century Roman person is an individual who lived within the Roman Empire during the 300s CE, shaped by the era’s political transformations, military conflicts, and the growing influence of Christianity.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:48 p.m.