Triple
T19106709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osman I |
E467675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman dynasty member |
C18043
|
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 dynasty member Context triple: [Osman I, instanceOf, Ottoman dynasty member]
-
A.
member of the Ottoman dynasty
chosen
A member of the Ottoman dynasty is an individual belonging by birth or marriage to the ruling imperial family of the Ottoman Empire, historically entitled to varying degrees of political influence, privilege, and succession rights.
-
B.
Salian dynasty member
A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
-
C.
member of the Mughal dynasty
A member of the Mughal dynasty is an individual belonging by birth or marriage to the imperial Timurid-origin ruling family that governed large parts of the Indian subcontinent from the early 16th to the mid-19th century.
-
D.
member of the Isaurian dynasty
A member of the Isaurian dynasty is an individual belonging to the Byzantine imperial family that ruled from the 8th to early 9th century, originating from the Isauria region in Asia Minor and known for initiating major religious and administrative reforms.
-
E.
member of the Battiad dynasty
A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.