Triple
T31529845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayor of the Palace of Austrasia |
E804446
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankish office |
C27921
|
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 office Context triple: [Mayor of the Palace of Austrasia, instanceOf, Frankish office]
-
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.
mayor of the palace
chosen
The mayor of the palace was the chief administrative officer of the royal household in early medieval Frankish kingdoms, who gradually became the real holder of political power behind the nominal king.
-
C.
Frankish person
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.
-
D.
Carolingian march
A Carolingian march was a frontier border territory of the Carolingian Empire, governed by a margrave and organized for military defense and administration against external threats.
-
E.
Frankish emperor
A Frankish emperor is a sovereign ruler from the Frankish people who held imperial authority in Western and Central Europe, most notably exemplified by Charlemagne and his successors in the early Middle Ages.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10 p.m.