Triple
T12603341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolingian County of Barcelona |
E300912
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian frontier county |
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 frontier county Context triple: [Carolingian County of Barcelona, instanceOf, Carolingian frontier county]
-
A.
Carolingian frontier march
A Carolingian frontier march was a militarized border territory of the Carolingian Empire, governed by a margrave and designed to defend and expand imperial frontiers.
-
B.
Carolingian march
chosen
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.
-
C.
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.
-
D.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
-
E.
medieval count
A medieval count is a nobleman who governed a county on behalf of a king or higher lord, overseeing administration, justice, and military defense within his territory.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:10 p.m.