Triple
T11349700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marca Hispanica |
E268809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian frontier march |
C30022
|
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 march Context triple: [Marca Hispanica, instanceOf, Carolingian frontier march]
-
A.
Count of Soissons
The Count of Soissons was a medieval noble title associated with the governance and control of the County of Soissons in northern France, often held by influential aristocratic families involved in regional and royal politics.
-
B.
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.
-
C.
Count of Vermandois
The Count of Vermandois was a medieval noble title in northern France, held by various influential families who governed the county of Vermandois and played significant roles in Frankish and Capetian politics.
-
D.
Count of Boulogne
The Count of Boulogne was a medieval noble title associated with the County of Boulogne in northern France, held by various influential lords who controlled this strategically important coastal region.
-
E.
Count of Provence
The Count of Provence is a noble title historically held by the ruler of the County of Provence, a medieval feudal territory in what is now southeastern France, signifying both regional governance and aristocratic status.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.