Triple
T17120235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Republican primary, 2008 |
E415443
|
entity |
| Predicate | hadEarlyVoting |
P60213
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Florida Republican primary, 2008, hadEarlyVoting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEarlyVoting Context triple: [Florida Republican primary, 2008, hadEarlyVoting, true]
-
A.
wasEarlyElection
Indicates that an election was held earlier than its originally scheduled or expected date.
-
B.
hasPrepollVoting
chosen
Indicates that an election or voting event includes the option for voters to cast their ballots before the official polling day.
-
C.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
D.
usedForEarlyElection
Indicates that something serves as a means or mechanism to trigger or conduct an election earlier than originally scheduled.
-
E.
hasInPersonVoting
Indicates that an election or decision-making process includes the option for participants to cast their votes physically at a designated location.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8092b548190b45c1695be47edc2 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.