Triple
T26390819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowdall system |
E663406
|
entity |
| Predicate | voterAction |
P42210
|
FINISHED |
| Object | ranks candidates in order of preference |
—
|
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: ranks candidates in order of preference | Statement: [Dowdall system, voterAction, ranks candidates in order of preference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voterAction Context triple: [Dowdall system, voterAction, ranks candidates in order of preference]
-
A.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
B.
voterApproval
Indicates that a voter has given consent, support, or positive endorsement to a proposal, candidate, or decision.
-
C.
votingIs
chosen
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
D.
voted
Indicates that an entity formally expressed a choice or decision, typically in an election, poll, or decision-making process, regarding another entity or option.
-
E.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bf1e248190a186aed862513478 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:25 p.m.