Triple
T9141453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine Ypsilantis |
E219335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Phanariote prince |
C17081
|
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: Phanariote prince Context triple: [Constantine Ypsilantis, instanceOf, Phanariote prince]
-
A.
Prince of Bulgaria
A Prince of Bulgaria is a male royal titleholder, typically a son or close male relative of the reigning Bulgarian monarch, who holds a defined place in the line of succession and represents the Bulgarian royal family in ceremonial and dynastic roles.
-
B.
prince of Wallachia
chosen
A prince of Wallachia is the sovereign ruler of the historical principality of Wallachia, responsible for governing its territories, leading its military, and navigating complex regional politics, often under the influence or suzerainty of larger neighboring powers.
-
C.
Russian prince
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor states.
-
D.
Armenian prince
An Armenian prince is a nobleman of Armenia’s historical aristocracy, often ruling a principality or region and serving as a military and political leader within the Armenian kingdom or under foreign suzerainty.
-
E.
Crimean khan
A Crimean khan was the sovereign ruler of the Crimean Khanate, a Turkic-Mongol state that existed from the 15th to the 18th century under the suzerainty of the Ottoman Empire.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:19 p.m.