Triple
T31220645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gennadius |
E796000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Exarch of Africa |
C57497
|
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: Exarch of Africa Context triple: [Gennadius, instanceOf, Exarch of Africa]
-
A.
Exarch of Ravenna
The Exarch of Ravenna was the Byzantine emperor’s chief governor in Italy from the late 6th to mid-8th century, combining supreme civil and military authority to defend and administer the remaining imperial territories in the West.
-
B.
Patriarch of Alexandria
The Patriarch of Alexandria is the senior ecclesiastical leader and bishop who heads one of the historic Christian patriarchates based in Alexandria, traditionally overseeing the spiritual and administrative affairs of the church in Egypt and surrounding regions.
-
C.
Archbishop of Constantinople
The Archbishop of Constantinople is the senior bishop and spiritual leader of the Eastern Orthodox Church in the city of Constantinople (modern-day Istanbul), traditionally holding the title of Ecumenical Patriarch and serving as "first among equals" among Orthodox bishops.
-
D.
Archbishop of Antioch
The Archbishop of Antioch is a senior ecclesiastical leader who serves as the chief bishop and spiritual head of a major Christian see historically centered in the ancient city of Antioch.
-
E.
praefectus Augustalis
The praefectus Augustalis was the Roman imperial governor of Egypt, a high-ranking equestrian official directly appointed by the emperor to administer the province’s civil, judicial, and financial affairs.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.