Triple
T32405251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop Colmán of Lindisfarne |
E828058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 7th-century Christian cleric |
C57935
|
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 Christian cleric Context triple: [Bishop Colmán of Lindisfarne, instanceOf, 7th-century Christian cleric]
-
A.
6th-century Italian bishop
A 6th-century Italian bishop is a high-ranking Christian cleric in Italy during the 500s who oversaw a diocese’s spiritual life, church administration, and relations with emerging post-Roman political powers.
-
B.
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.
-
C.
medieval Christian monk
A medieval Christian monk is a religious man who lives in a monastic community under vows of poverty, chastity, and obedience, dedicating his life to prayer, work, and spiritual study within the Christian tradition.
-
D.
Catholic monk
A Catholic monk is a man who has taken religious vows within the Catholic Church and lives in a community or cloister dedicated to prayer, work, and spiritual discipline.
-
E.
Syriac Christian monk
A Syriac Christian monk is a member of an ascetic religious community within the Syriac Christian tradition, devoted to prayer, contemplation, and communal or solitary monastic life shaped by Syriac liturgy, language, and theology.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.