Triple
T14408636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecgbert of York |
E357266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon churchman |
C27802
|
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: Anglo-Saxon churchman Context triple: [Ecgbert of York, instanceOf, Anglo-Saxon churchman]
-
A.
Anglo-Saxon bishop
An Anglo-Saxon bishop was a high-ranking ecclesiastical leader in early medieval England responsible for overseeing a diocese, administering sacraments, guiding clergy and laity, and often advising kings in both religious and political matters.
-
B.
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.
-
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.
Anglo-Norman cleric
An Anglo-Norman cleric is a religious official of the medieval Christian Church in England or Normandy after the Norman Conquest, typically involved in ecclesiastical administration, pastoral care, and the transmission of Latin learning within an Anglo-Norman cultural context.
-
E.
Northumbrian cleric
chosen
A Northumbrian cleric is a religious scholar and church official from the early medieval Anglo-Saxon kingdom of Northumbria, responsible for spiritual leadership, liturgical duties, and the preservation and production of Christian learning and manuscripts.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.