Triple
T357986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 United States presidential election |
E7585
|
entity |
| Predicate | votingTechnologyIssue |
P2726
|
FINISHED |
| Object | punch-card ballots |
—
|
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: punch-card ballots | Statement: [2000 United States presidential election, votingTechnologyIssue, punch-card ballots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingTechnologyIssue Context triple: [2000 United States presidential election, votingTechnologyIssue, punch-card ballots]
-
A.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
B.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
C.
votingMethod
chosen
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
D.
voteCertificationBy
Indicates that a vote or election result has been formally certified or validated by a specified entity.
-
E.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebb0e348819086e3ccd96c7b129e |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e959ce948190a201c017eecb7c95 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.