Triple
T22615704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | beylerbey |
E558139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman administrative title |
C17083
|
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: Ottoman administrative title Context triple: [beylerbey, instanceOf, Ottoman administrative title]
-
A.
Ottoman court title
chosen
An Ottoman court title is an official designation granted within the Ottoman imperial hierarchy that denotes a person's rank, role, and privileges in the administration, judiciary, or royal household.
-
B.
Turkic title
A Turkic title is an honorific or rank designation historically used by Turkic-speaking peoples to denote social status, political authority, military rank, or noble lineage.
-
C.
Hungarian noble title
A Hungarian noble title is a hereditary or granted rank within the historical social hierarchy of the Kingdom of Hungary, denoting status, privileges, and obligations among the nobility.
-
D.
Ottoman vassal ruler
An Ottoman vassal ruler was a semi-autonomous local sovereign who governed a territory under the suzerainty of the Ottoman Empire, owing tribute, military support, and political loyalty while retaining limited internal authority.
-
E.
ancient Roman title
An ancient Roman title is a formal designation or rank used in Roman society and government to denote an individual's official role, status, or authority within the political, military, religious, or social hierarchy.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 2:59 p.m.