Triple
T22791633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hincmar of Reims |
E564126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankish cleric |
C12764
|
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: Frankish cleric Context triple: [Hincmar of Reims, instanceOf, Frankish cleric]
-
A.
Frankish bishop
A Frankish bishop was a high-ranking cleric in the Frankish kingdoms who oversaw Christian religious life, administered dioceses, and often played significant political and cultural roles in early medieval Europe.
-
B.
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.
-
C.
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.
-
D.
Breton priest
A Breton priest is a Catholic cleric from the Brittany region of France who serves local parishes, often preserving and promoting Breton language, culture, and religious traditions.
-
E.
Carolingian intellectual
chosen
A Carolingian intellectual is a learned figure of the 8th–9th century Frankish realm who engaged in the study, preservation, and reform of classical, Christian, and legal texts to support the cultural and administrative renewal of the Carolingian Empire.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:30 p.m.