Triple
T26584713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas elections |
E667175
|
entity |
| Predicate | useVotingSystem |
P110753
|
FINISHED |
| Object | secret ballot |
—
|
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: secret ballot | Statement: [Kansas elections, useVotingSystem, secret ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useVotingSystem Context triple: [Kansas elections, useVotingSystem, secret ballot]
-
A.
usesVotingBallots
chosen
Indicates that one entity conducts or participates in a voting process by employing ballots as the method for casting votes.
-
B.
usesVotingBody
Indicates that one entity employs or relies on a particular voting body to make decisions or take actions on its behalf.
-
C.
usesVotingSystemForHead
Indicates that a particular voting system is employed to select or appoint the head (leader) of an entity.
-
D.
usesVotingDiscipline
Indicates that an entity follows or enforces a coordinated pattern of voting behavior, typically aligning votes according to a shared strategy, rule, or group directive.
-
E.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614e47cdc81909786f92cc0d5965f |
completed | May 2, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:05 a.m.