Triple
T29545406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Belz |
E749616
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ruthenian noble title |
C55881
|
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: Ruthenian noble title Context triple: [Prince of Belz, instanceOf, Ruthenian noble title]
-
A.
Polish noble title
A Polish noble title is a hereditary or granted rank within the historical Polish–Lithuanian nobility (szlachta), denoting social status, privileges, and often specific duties in the political and military hierarchy.
-
B.
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.
-
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.
Swedish noble title
A Swedish noble title is a hereditary or granted rank of nobility in Sweden, historically conferring social status, privileges, and often responsibilities within the Swedish aristocratic hierarchy.
-
E.
Polish noble office
A Polish noble office is a formal position or title within the historical governance and social hierarchy of the Polish–Lithuanian Commonwealth, held by members of the nobility (szlachta) and associated with specific administrative, judicial, or ceremonial duties.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:07 p.m.