Triple
T2493542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Chad |
E52101
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 7th-century bishop |
C518
|
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: 7th-century bishop Context triple: [Saint Chad, instanceOf, 7th-century 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.
Syriac Christian bishop
A Syriac Christian bishop is a high-ranking cleric within the Syriac Christian traditions who oversees dioceses, administers sacraments, preserves Syriac liturgical and theological heritage, and provides spiritual and administrative leadership to clergy and laity.
-
C.
Anglo-Saxon abbot
An Anglo-Saxon abbot was the head of a monastic community in early medieval England, overseeing its spiritual life, administration, landholdings, and relations with secular and ecclesiastical authorities.
-
D.
Catholic bishop
chosen
A Catholic bishop is a high-ranking ordained minister in the Catholic Church who possesses the fullness of the sacrament of Holy Orders and is responsible for teaching doctrine, governing a diocese, and sanctifying the faithful through the sacraments.
-
E.
Anglo-Saxon monk
An Anglo-Saxon monk is a member of a Christian religious community in early medieval England, devoted to prayer, learning, manuscript production, and the observance of monastic rules.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:45 p.m.