Triple
T31762794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberic II of Spoleto |
E810725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | de facto ruler of Rome |
C57586
|
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: de facto ruler of Rome Context triple: [Alberic II of Spoleto, instanceOf, de facto ruler of Rome]
-
A.
regent of the Western Roman Empire
A regent of the Western Roman Empire was an individual who governed the empire on behalf of an underage, absent, or otherwise incapacitated Western Roman emperor, exercising imperial authority without holding the imperial title.
-
B.
ruler of the Papal States
A ruler of the Papal States is the sovereign authority, historically the Pope, who governed the territories under direct papal control in central Italy, exercising both spiritual leadership and temporal political power.
-
C.
imperial prince of Rome
An imperial prince of Rome is a male member of the ruling emperor’s family, often positioned as a potential heir and endowed with high status, privileges, and political influence within the Roman imperial hierarchy.
-
D.
regent of the Eastern Roman Empire
A regent of the Eastern Roman Empire is an appointed or self-declared authority who governs the empire on behalf of a reigning but underage, absent, incapacitated, or otherwise unable emperor, wielding imperial power without holding the imperial title.
-
E.
ruler of Italy
A ruler of Italy is a sovereign or head of state who holds ultimate political authority over the Italian territory and its people during a specific historical period.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:31 p.m.