Triple
T11406410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish March |
E270250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian march |
C29983
|
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: Carolingian march Context triple: [Spanish March, instanceOf, Carolingian march]
-
A.
Carolingian
Carolingian refers to the dynasty and cultural era in early medieval Western Europe (8th–10th centuries) associated with Charlemagne and his successors, marked by political consolidation, religious reform, and a revival of learning and the arts.
-
B.
Carolingian successor state
A Carolingian successor state is a political entity that emerged from the fragmentation of the Carolingian Empire, inheriting and adapting its territorial, institutional, and cultural legacy in medieval Europe.
-
C.
King of Lotharingia
The King of Lotharingia is the sovereign ruler of the medieval kingdom of Lotharingia, governing its territories, administering justice, leading its armies, and representing its authority within the broader context of the Frankish and later Holy Roman Empire realms.
-
D.
Duke of Lotharingia
The Duke of Lotharingia is a high-ranking noble who governs the historical region of Lotharingia, wielding military, judicial, and administrative authority on behalf of the sovereign.
-
E.
imperial state of the Holy Roman Empire
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
- F. None of above. chosen
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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:34 p.m.