Triple
T36121511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dux Olsnensis |
E1044754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Latin noble title |
C1369
|
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: medieval Latin noble title Context triple: [dux Olsnensis, instanceOf, medieval Latin noble title]
-
A.
medieval court title
A medieval court title is a formal designation granted to an individual within a royal or noble household, defining their rank, duties, and privileges in the governance, ceremony, or administration of the realm.
-
B.
medieval Latin name
chosen
A medieval Latin name is a personal or place designation used in the Middle Ages, typically rendered in Latinized form to align with ecclesiastical, scholarly, or administrative conventions of the period.
-
C.
Byzantine noble title
A Byzantine noble title is a formal rank or honorific designation within the hierarchical aristocratic and court system of the Byzantine Empire, signifying status, authority, and often specific administrative or military responsibilities.
-
D.
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.
-
E.
medieval nobility
Medieval nobility comprised the hereditary warrior-elite who held land from a monarch in exchange for military and political service, dominating social, economic, and legal life in feudal Europe.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.