Triple
T3828483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Baldred of Tyninghame |
E88750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Northumbrian person |
C4948
|
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: medieval Northumbrian person Context triple: [Saint Baldred of Tyninghame, instanceOf, medieval Northumbrian person]
-
A.
11th-century English person
An 11th-century English person is an individual who lived in England between 1001 and 1100 CE, experiencing the social, political, and cultural transformations surrounding events like the Norman Conquest.
-
B.
Scottish knight
A Scottish knight is a medieval mounted warrior of Scottish origin, bound by chivalric codes and feudal allegiance, distinguished by regional arms, armor, and participation in Scotland’s historic conflicts.
-
C.
14th-century English person
A 14th-century English person is an individual living in England between 1301 and 1400, shaped by medieval feudal society, the Black Death, the Hundred Years’ War, and the evolving English language and culture of the late Middle Ages.
-
D.
Anglo-Saxon monk
chosen
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.
-
E.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.