Triple
T19442213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvet de Couvrai |
E486377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary politician |
C26299
|
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: revolutionary politician Context triple: [Louvet de Couvrai, instanceOf, revolutionary politician]
-
A.
revolutionary statesman
A revolutionary statesman is a political leader who combines visionary, transformative ideals with practical governance to fundamentally reshape a state’s institutions, power structures, and social order.
-
B.
Radical politician
chosen
A radical politician is a public office seeker or holder who advocates for fundamental, often rapid and systemic changes to existing political, economic, or social structures, typically challenging mainstream ideologies and institutions.
-
C.
revolutionary democrat
A revolutionary democrat is an individual who seeks to achieve democratic governance and social equality through radical, often transformative political change, potentially including the use of mass mobilization or insurrection against authoritarian or oligarchic systems.
-
D.
reformist leader
A reformist leader is an individual in a position of authority who seeks to change existing systems, policies, or institutions through gradual, structured, and often legally grounded improvements rather than radical or revolutionary means.
-
E.
politician
A politician is a person who seeks or holds public office and engages in activities related to governance, policy-making, and representing the interests of constituents within a political system.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.