Triple
T33467247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berhane Meskel Redda |
E857087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ethiopian revolutionary |
C48340
|
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: Ethiopian revolutionary Context triple: [Berhane Meskel Redda, instanceOf, Ethiopian revolutionary]
-
A.
Ethiopian politician
chosen
An Ethiopian politician is a public figure who participates in the governance and political decision-making processes of Ethiopia, often holding elected or appointed office at the local, regional, or national level.
-
B.
Eritrean politician
An Eritrean politician is a public figure from Eritrea who engages in governance, policy-making, and political leadership at local, regional, or national levels within the country's political system.
-
C.
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.
-
D.
Somali leader
A Somali leader is an individual who holds a position of authority or influence within Somali society or governance, guiding political, social, or community affairs at local, regional, or national levels.
-
E.
Hungarian revolutionary
A Hungarian revolutionary is an individual from Hungary who actively participates in or leads movements aimed at radically transforming the country’s political, social, or national order, often through organized resistance or uprising.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.