Triple
T6436803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Serbia (Ottoman) |
E129917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | client state of the Habsburg monarchy |
C20135
|
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: client state of the Habsburg monarchy Context triple: [Kingdom of Serbia (Ottoman), instanceOf, client state of the Habsburg monarchy]
-
A.
Habsburg
Habsburg: A powerful European royal dynasty that ruled vast territories including the Holy Roman Empire, Spain, and Austria for centuries through strategic marriages and political alliances.
-
B.
Habsburg monarch
A Habsburg monarch is a sovereign ruler from the Habsburg dynasty, which dominated Central European and Spanish thrones for centuries through strategic marriages and dynastic inheritance.
-
C.
institution of the Kingdom of Hungary
An institution of the Kingdom of Hungary is an organized body or establishment—political, legal, religious, educational, or administrative—that operated within and under the authority of the historical Kingdom of Hungary.
-
D.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
-
E.
French client state
A French client state is a nominally independent country that is politically, economically, or militarily subordinate to France and significantly influenced or controlled by French interests.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:45 p.m.