Triple
T19393878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian presidential election, 2014 |
E485136
|
entity |
| Predicate | lastVotingDayExtension |
P28288
|
FINISHED |
| Object | 2014-05-28 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2014-05-28 | Statement: [Egyptian presidential election, 2014, lastVotingDayExtension, 2014-05-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastVotingDayExtension Context triple: [Egyptian presidential election, 2014, lastVotingDayExtension, 2014-05-28]
-
A.
ballotingDays
chosen
Indicates the specific days or period during which voting or balloting is conducted.
-
B.
vetoOverrideDate
Indicates the date on which a veto was formally overridden by the relevant decision-making body.
-
C.
votingTiming
Indicates the temporal relationship specifying when a voting action occurs relative to a defined event or period.
-
D.
vetoDate
Indicates the date on which a veto action was formally made or recorded.
-
E.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
- F. None of above.
Provenance (3 batches)
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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b47630881909ba390888b8779f6 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.