Triple
T32851581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juror 5 |
E840265
|
entity |
| Predicate | changesVote |
P177801
|
FINISHED |
| Object | from "guilty" to "not guilty" |
—
|
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: from "guilty" to "not guilty" | Statement: [Juror 5, changesVote, from "guilty" to "not guilty"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changesVote Context triple: [Juror 5, changesVote, from "guilty" to "not guilty"]
-
A.
votesForChange
Indicates that an entity expresses support for or chooses an option aimed at altering an existing state, policy, or condition.
-
B.
introducedVotingSystemChange
Indicates that an entity initiated or implemented a modification to an existing voting system.
-
C.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
D.
voterTurnoutChange
Indicates the amount or direction of change in voter turnout between two elections or time periods.
-
E.
voteOn
Indicates that an entity formally expresses a choice or decision regarding a specific proposal, issue, or candidate.
- F. None of above. chosen
Provenance (4 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:17 a.m.