Triple
T35822113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hospers |
E1035531
|
entity |
| Predicate | electoralVoteYear |
P199862
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [John Hospers, electoralVoteYear, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralVoteYear Context triple: [John Hospers, electoralVoteYear, 1972]
-
A.
electoralVoteFor
Indicates that a specified number of electoral votes are allocated or cast in favor of a particular candidate or option in an election.
-
B.
electoralVotesReceived
Indicates that one entity received a specified number of electoral votes in an election from another entity or jurisdiction.
-
C.
electorsCensusYear
Indicates the specific census year associated with the recorded electors in the relationship.
-
D.
electoralVoteOutcome
Indicates the result of an election in terms of how electoral votes are allocated or distributed among candidates or options.
-
E.
reElectionYear
Indicates the year in which an entity is (or is scheduled to be) elected again to the same position or office.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69ff5f5ddfcc819092563419f9e82d60 |
completed | May 9, 2026, 4:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.