Triple
T20065505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian presidential elections |
E499595
|
entity |
| Predicate | relatedInstitution |
P9446
|
FINISHED |
| Object | Islamic Revolutionary Guard Corps (IRGC) |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Islamic Revolutionary Guard Corps (IRGC) Context triple: [Iranian presidential elections, relatedInstitution, Islamic Revolutionary Guard Corps (IRGC)]
-
A.
Islamic Revolutionary Guard Corps
chosen
The Islamic Revolutionary Guard Corps is a powerful branch of Iran’s armed forces, created after the 1979 revolution, that wields significant military, political, and economic influence both inside Iran and across the region.
-
B.
Quds Force
The Quds Force is an elite unit of Iran’s Islamic Revolutionary Guard Corps responsible for conducting foreign military, intelligence, and covert operations to advance Iranian interests abroad.
-
C.
IRGC Intelligence Organization
The IRGC Intelligence Organization is a powerful Iranian security and intelligence agency controlled by the Islamic Revolutionary Guard Corps, responsible for internal surveillance, counterintelligence, and suppressing political dissent.
-
D.
People's Guard
The People's Guard was the armed resistance organization of the Polish Workers' Party that fought against Nazi occupation in Poland during World War II.
-
E.
Islamic Republic of Iran Army
The Islamic Republic of Iran Army is Iran’s regular, conventional military force responsible for defending the country’s territorial integrity on land, at sea, and in the air.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:39 p.m.