Triple
T17942325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armen Garo |
E448615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian revolutionary |
C24767
|
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: Armenian revolutionary Context triple: [Armen Garo, instanceOf, Armenian 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 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.
-
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.
Armenian Revolutionary Federation member
chosen
An Armenian Revolutionary Federation member is an individual who belongs to the ARF political party, supporting its Armenian nationalist, socialist, and often diaspora-focused agenda through political, social, or organizational activities.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.