Triple
T4421505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viewer's Choice Award |
E95106
|
entity |
| Predicate | platformUsedForVoting |
P28726
|
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: [Viewer's Choice Award, platformUsedForVoting, online voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformUsedForVoting Context triple: [Viewer's Choice Award, platformUsedForVoting, online voting]
-
A.
platformUsed
chosen
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
-
B.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
C.
popularVoteUsedFor
Indicates that the outcome of a popular vote is used as the basis or input for determining or deciding something.
-
D.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
E.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35521e020819099e72b9e2ccbd36d |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.