Triple
T36433528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eggihard |
E897506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankish royal official |
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 royal official Context triple: [Eggihard, instanceOf, Frankish royal official]
-
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.
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.
-
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.
Merovingian ruler
A Merovingian ruler is a king or queen from the Frankish Merovingian dynasty (5th–8th centuries) who exercised political, military, and religious authority over early medieval Gaul and surrounding regions.
-
E.
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.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.