Triple
T18875165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kebbede Guebre |
E461663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ethiopian military personnel |
C41437
|
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 military personnel Context triple: [Kebbede Guebre, instanceOf, Ethiopian military personnel]
-
A.
Libyan military personnel
Libyan military personnel are individuals who serve in Libya’s armed forces, including the army, navy, air force, and associated security units, responsible for national defense and internal security.
-
B.
Turkmen troops
Turkmen troops are military forces composed primarily of ethnic Turkmen soldiers, historically serving in various regional armies and contemporary national armed forces, often reflecting Turkmen cultural, political, and strategic interests.
-
C.
Laotian military personnel
Laotian military personnel are individuals who serve in the armed forces of Laos, responsible for national defense, internal security, and supporting government operations.
-
D.
Afghan military leaders
Afghan military leaders are influential figures who have commanded armed forces or factions in Afghanistan, shaping the country’s security, politics, and conflicts through their strategic, ideological, and often regional power bases.
-
E.
Russian military personnel
Russian military personnel are individuals who serve in the armed forces of the Russian Federation, including its army, navy, aerospace forces, and other military branches, performing roles related to national defense, security, and military operations.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.