Triple
T15747066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelu Voican Voiculescu |
E381746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanian revolutionary |
C35825
|
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 revolutionary Context triple: [Gelu Voican Voiculescu, instanceOf, Romanian revolutionary]
-
A.
Bulgarian revolutionary
A Bulgarian revolutionary is an individual actively engaged in organizing, leading, or participating in political and social struggles aimed at liberating Bulgaria from oppression and transforming its societal order.
-
B.
Soviet revolutionary
A Soviet revolutionary is an individual who actively participated in or supported the political, social, and often armed struggle to overthrow the existing order and establish or advance the socialist state in the former Soviet Union.
-
C.
Romanian national unification
Romanian national unification is the historical and political process through which Romanian-speaking populations and territories sought to consolidate into a single nation-state, culminating in the formation and later expansion of modern Romania.
-
D.
Georgian revolutionary
A Georgian revolutionary is an individual from Georgia who actively participates in or leads radical political, social, or national movements aimed at overthrowing existing power structures and transforming society.
-
E.
Corsican patriot
A Corsican patriot is an individual deeply devoted to the island of Corsica, actively supporting its cultural identity, political autonomy, and historical legacy.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.