Triple
T18170043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mihail Kogălniceanu |
E434999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanian statesman |
C39829
|
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 statesman Context triple: [Mihail Kogălniceanu, instanceOf, Romanian statesman]
-
A.
Romanian revolutionary
A Romanian revolutionary is an individual from Romania who actively participates in or leads movements aimed at radically transforming the country’s political, social, or economic systems, often through protest, activism, or insurrection.
-
B.
Hungarian politician
A Hungarian politician is a public figure who participates in the governance and political decision-making processes of Hungary, typically by holding or seeking elected or appointed office at the local, regional, or national level.
-
C.
Montenegrin statesman
A Montenegrin statesman is a political leader or public official from Montenegro who plays a significant role in shaping the country's domestic and foreign policies through governance, diplomacy, and public service.
-
D.
Belgian statesman
A Belgian statesman is a prominent political leader from Belgium who plays a key role in shaping the nation’s domestic and foreign policies through high-level governmental or diplomatic service.
-
E.
Austro-Hungarian statesman
An Austro-Hungarian statesman is a high-ranking political leader or government official who played a significant role in shaping the policies, diplomacy, and administration of the Austro-Hungarian Empire.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:30 a.m.