Triple
T34302815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Nicholas of Romania |
E880224
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanian prince |
C61526
|
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: Romanian prince Context triple: [Prince Nicholas of Romania, instanceOf, Romanian prince]
-
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.
King of Romania
The King of Romania is the hereditary monarch who historically served as the head of state of Romania, embodying national unity and representing the country in domestic and international affairs.
-
C.
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.
-
D.
ruler of Moldavia
A ruler of Moldavia is the sovereign leader who historically governed the principality of Moldavia, overseeing its political, military, and administrative affairs.
-
E.
Polish prince
A Polish prince is a male member of the historical Polish nobility or royal family, often holding hereditary titles, lands, and political influence within the Polish–Lithuanian Commonwealth or its predecessor states.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.