Triple
T30088238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Urban I |
E764656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 3rd-century Christian leader |
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 Christian leader Context triple: [Pope Urban I, instanceOf, 3rd-century Christian leader]
-
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.
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.
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.
-
D.
late 5th-century religious leader
A late 5th-century religious leader is an influential spiritual figure who guided the beliefs, practices, and organization of a religious community during the closing decades of the 400s CE.
-
E.
4th-century Christian martyr
A 4th-century Christian martyr is an individual who was killed during the 300s CE for steadfastly professing and practicing the Christian faith, often under Roman imperial persecution.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:04 p.m.