Triple
T17957295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Cornelius |
E448985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 3rd-century pope |
C18623
|
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: 3rd-century pope Context triple: [Saint Cornelius, instanceOf, 3rd-century pope]
-
A.
3rd-century Christian bishop
chosen
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.
-
B.
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.
-
C.
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.
-
D.
3rd-century ruler
A 3rd-century ruler is a sovereign or governing authority who held power during the years 200–299 CE, navigating the political, military, and social upheavals characteristic of that era.
-
E.
3rd-century Roman emperor
A 3rd-century Roman emperor is the sovereign ruler of the Roman Empire during the 200s CE, navigating intense military, political, and economic crises while asserting imperial authority over a vast and often unstable realm.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.