Triple
T4544753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian constitutional referendum, 2011 |
E110018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | election in Egypt |
C13361
|
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: election in Egypt Context triple: [Egyptian constitutional referendum, 2011, instanceOf, election in Egypt]
-
A.
election in the Soviet Union
An election in the Soviet Union was a state-controlled political process in which candidates, typically preselected by the Communist Party, were formally approved by voters in largely non-competitive, single-party ballots.
-
B.
presidential election
A presidential election is a formal, periodic process in which eligible voters select a head of state or government, typically through a structured system of campaigns, ballots, and vote counting governed by constitutional or legal rules.
-
C.
political election
chosen
A political election is a formal decision-making process in which eligible citizens or members of a group vote to choose individuals or parties to hold public office or represent their interests in governance.
-
D.
Soviet election
A Soviet election was a state-controlled, non-competitive electoral process in the USSR, typically featuring a single approved candidate per seat and serving primarily to legitimize Communist Party rule rather than to offer genuine voter choice.
-
E.
2019 election
The 2019 election class represents a specific electoral event held in the year 2019, encapsulating its candidates, parties, results, and associated political context.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.