Triple
T35822111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hospers |
E1035531
|
entity |
| Predicate | receivedElectoralVote |
P107366
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [John Hospers, receivedElectoralVote, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedElectoralVote Context triple: [John Hospers, receivedElectoralVote, yes]
-
A.
electoralVotesReceived
Indicates that one entity received a specified number of electoral votes in an election from another entity or jurisdiction.
-
B.
resolvedElectoralVotesFrom
Indicates that a set of electoral votes has been officially determined or allocated based on the outcome associated with a particular source (such as a state, district, or election event).
-
C.
heldElectoralVoteFor
Indicates that an elector or jurisdiction cast its official electoral vote in favor of a particular candidate in an election.
-
D.
hasElectoralVoteIn
chosen
Indicates that an entity possesses or receives electoral votes within a specified election or jurisdiction.
-
E.
electoralVoteFor
Indicates that a specified number of electoral votes are allocated or cast in favor of a particular candidate or option in an 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.