Triple
T18250042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea Player of the Year |
E437064
|
entity |
| Predicate | typicalVotingMedium |
P26341
|
FINISHED |
| Object | online 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: online voting | Statement: [Chelsea Player of the Year, typicalVotingMedium, online voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVotingMedium Context triple: [Chelsea Player of the Year, typicalVotingMedium, online voting]
-
A.
typicalVoters
Indicates that the subject entity is a representative or characteristic member of the group of voters associated with the object entity.
-
B.
popularVoteType
chosen
Indicates the specific method or category by which a popular vote is conducted or classified in an election or decision process.
-
C.
popularVote
Indicates the number or share of votes directly cast by the general electorate for a candidate or option in an election.
-
D.
typicalPresidentialVote
Indicates that the vote cast aligns with the usual or characteristic voting pattern observed in presidential elections.
-
E.
mediaTypeOfVoters
Indicates the type or category of media associated with or used by the voters.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd8065b08190ae8d37102141f470 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.