Triple
T25334649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Players Choice Award for Player of the Year |
E635242
|
entity |
| Predicate | hasVoterType |
P38956
|
FINISHED |
| Object | peer voting |
—
|
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: peer voting | Statement: [Players Choice Award for Player of the Year, hasVoterType, peer voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoterType Context triple: [Players Choice Award for Player of the Year, hasVoterType, peer voting]
-
A.
hasTypeOfVoters
chosen
Indicates that an entity is associated with or characterized by a particular category or kind of voters.
-
B.
hasBallotType
Indicates that an election, ballot, or voting process uses or is associated with a specific type or format of ballot.
-
C.
hasElectionType
Indicates the specific category or kind of election associated with a given electoral event or process.
-
D.
hasVoterRegister
Indicates that an entity maintains or possesses an official register or list of eligible voters.
-
E.
voterRegistrationType
Indicates the specific category or method by which a person is registered to vote (e.g., in-person, mail-in, online, or same-day registration).
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:32 p.m.