Triple
T7513760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperium Romaniae |
E177589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin Empire |
C22495
|
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: Latin Empire Context triple: [Imperium Romaniae, instanceOf, Latin Empire]
-
A.
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.
-
B.
Bulgar state
A Bulgar state is a political entity historically founded and ruled by the Bulgar people, typically characterized by a semi-nomadic warrior elite governing settled agricultural populations within a defined territory.
-
C.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
D.
Despot of the Morea
The Despot of the Morea was a Byzantine imperial title granted to a ruler governing the semi-autonomous province of the Morea (Peloponnese), often held by members of the imperial family as a regional appanage.
-
E.
Eurasian empire
A Eurasian empire is a vast, centralized political entity that spans significant territories across both Europe and Asia, integrating diverse cultures, economies, and governance systems under a single imperial authority.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:45 p.m.