Triple
T6466513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine theme of Syria |
E142245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military-administrative province |
C13035
|
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: military-administrative province Context triple: [Byzantine theme of Syria, instanceOf, military-administrative province]
-
A.
military administrative division
chosen
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
B.
Eyalet
An Eyalet is a major administrative division of the Ottoman Empire, governed by a beylerbey and comprising several subordinate districts or sanjaks.
-
C.
Chief Commissioner's Province
A Chief Commissioner's Province is a type of administrative division in which a territory is governed directly by a chief commissioner appointed by a central authority, rather than by a locally elected government.
-
D.
frontier province
A frontier province is a border region of a state or empire where central authority, culture, and control meet and interact with external or less-governed territories, often marked by strategic, economic, and cultural significance.
-
E.
military district of the Holy Roman Empire
A military district of the Holy Roman Empire was an administrative and territorial unit organized primarily for defense and military command, grouping various imperial estates under a regional military structure.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:49 p.m.