Triple
T36500128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertha (daughter of Charlemagne) |
E899301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval European person |
C3415
|
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 European person Context triple: [Bertha (daughter of Charlemagne), instanceOf, medieval European person]
-
A.
medieval Polish person
A medieval Polish person is an inhabitant of the historical Polish lands between roughly the 10th and 15th centuries, shaped by the Christianization of Poland, feudal social structures, and the political and cultural life of the Piast and early Jagiellonian realms.
-
B.
medieval European noble
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
-
C.
early medieval English person
An early medieval English person is an individual who lived in England roughly between the 5th and 11th centuries, shaped by a mix of Anglo-Saxon, Viking, and early Christian cultural, social, and political influences.
-
D.
medieval people
chosen
Medieval people are individuals living during the Middle Ages, typically characterized by feudal social structures, agrarian lifestyles, religious centrality, and limited technological development compared to later periods.
-
E.
European person
A European person is an individual who is a native or inhabitant of Europe, typically sharing cultural, historical, and/or political ties associated with the European continent.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.