Triple
T32339120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flavian II of Antioch |
E826259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 5th-century Christian bishop |
C57918
|
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: 5th-century Christian bishop Context triple: [Flavian II of Antioch, instanceOf, 5th-century Christian bishop]
-
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.
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.
-
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.
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.
-
E.
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.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:48 a.m.