Triple
T9569215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine Empire (as ally during 1453 siege) |
E230871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian empire |
C26032
|
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: Christian empire Context triple: [Byzantine Empire (as ally during 1453 siege), instanceOf, Christian empire]
-
A.
Christian kingdom
A Christian kingdom is a sovereign state whose governance, laws, and cultural identity are fundamentally shaped by Christian beliefs, institutions, and traditions.
-
B.
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.
-
C.
Crusader state
A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
-
D.
Islamic empire
An Islamic empire is a large, multi-ethnic political entity historically governed by Muslim rulers who derive authority from Islamic law and tradition, integrating religious, cultural, and administrative systems across vast territories.
-
E.
Roman Catholic church
A Roman Catholic church is a Christian place of worship that serves as a local community’s center for liturgy, sacraments, and prayer within the Roman Catholic tradition.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:04 p.m.