Triple
T8377687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria of Trebizond |
E197615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Trapezuntine imperial family |
C23968
|
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: member of the Trapezuntine imperial family Context triple: [Maria of Trebizond, instanceOf, member of the Trapezuntine imperial family]
-
A.
member of the Ottoman dynasty
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.
member of the Constantinian dynasty
A member of the Constantinian dynasty is an individual belonging to the imperial family that ruled the Roman Empire from the rise of Constantine the Great in the early 4th century until the death of his descendants later that century.
-
C.
member of the House of Lusignan
A member of the House of Lusignan is an individual belonging to the medieval French noble dynasty that rose to prominence as lords of Lusignan and later as kings of Jerusalem, Cyprus, and Armenia.
-
D.
member of the House of Romanov
A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
E.
member of the Billung dynasty
A member of the Billung dynasty is an individual belonging to the medieval German noble family that held significant ducal power in Saxony from the 10th to early 12th centuries.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:02 p.m.