Triple
T14823477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael I of Romania |
E348512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanian monarch |
C28288
|
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 monarch Context triple: [Michael I of Romania, instanceOf, Romanian monarch]
-
A.
King of Romania
chosen
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.
-
B.
Hungarian monarch
A Hungarian monarch is the sovereign ruler of the Kingdom of Hungary, historically holding supreme political, military, and often religious authority over the realm and its subjects.
-
C.
Tsar of Bulgaria
The Tsar of Bulgaria was the monarchic ruler of the Bulgarian state, holding supreme political and often religious authority over the country during its medieval and modern imperial periods.
-
D.
Eastern European monarch
An Eastern European monarch is a sovereign ruler—such as a king, queen, tsar, or grand duke—who governs or ceremonially represents a state in the Eastern European region, shaped by its distinct historical, cultural, and political traditions.
-
E.
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.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:51 a.m.