Triple
T31832090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotrude of Trier |
E812564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 8th-century Frankish person |
C30485
|
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: 8th-century Frankish person Context triple: [Rotrude of Trier, instanceOf, 8th-century Frankish person]
-
A.
Frankish person
chosen
A Frankish person is an individual belonging to the early medieval Germanic people known as the Franks, who inhabited regions of present-day France, Germany, and the Low Countries and played a central role in the formation of Western European kingdoms.
-
B.
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.
-
C.
10th-century German person
A 10th-century German person is an individual who lived in the German-speaking regions of Central Europe between 900 and 999 CE, shaped by the political, social, and cultural dynamics of the early Holy Roman Empire.
-
D.
Carolingian intellectual
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.
-
E.
Frankish prince
A Frankish prince is a male royal of the Frankish realms, typically a son or close male relative of a Frankish king, holding dynastic status, political influence, and often territorial authority within the kingdom.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:47 p.m.