Triple
T3632058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustine of Canterbury |
E76978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 6th-century Christian clergy |
C13525
|
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: 6th-century Christian clergy Context triple: [Augustine of Canterbury, instanceOf, 6th-century Christian clergy]
-
A.
group of Christian monks
A group of Christian monks is a community of men who live together under religious vows, dedicating their lives to prayer, contemplation, and communal service according to a shared monastic rule.
-
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.
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.
-
D.
Christian monastics
Christian monastics are individuals who dedicate their lives to God through vows such as poverty, chastity, and obedience, living in communities or solitude according to specific religious rules and traditions.
-
E.
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.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.