Triple
T18802027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen III of Moldavia |
E459778
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince of Moldavia |
C17082
|
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: Prince of Moldavia Context triple: [Stephen III of Moldavia, instanceOf, Prince of Moldavia]
-
A.
prince of Wallachia
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.
-
B.
ruler of Moldavia
chosen
A ruler of Moldavia is the sovereign leader who historically governed the principality of Moldavia, overseeing its political, military, and administrative affairs.
-
C.
Prince of Volhynia
A Prince of Volhynia was a medieval ruler of the Volhynia principality in the historical region of Ruthenia, exercising political, military, and administrative authority over its territories and people.
-
D.
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.
-
E.
Prince of Transylvania
A Prince of Transylvania is the sovereign or semi-sovereign ruler of the historical region of Transylvania, traditionally holding political, military, and often symbolic authority over its territories and people.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.