Triple
T13107048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Video of the Year |
E310868
|
entity |
| Predicate | hasVotingProcess |
P83077
|
FINISHED |
| Object | MTV-determined nomination process |
—
|
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: MTV-determined nomination process | Statement: [Video of the Year, hasVotingProcess, MTV-determined nomination process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingProcess Context triple: [Video of the Year, hasVotingProcess, MTV-determined nomination process]
-
A.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
-
B.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
C.
voteProcess
chosen
Indicates the formal procedure by which participants cast and record their votes to reach a decision or outcome.
-
D.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
E.
hasInPersonVoting
Indicates that an election or decision-making process includes the option for participants to cast their votes physically at a designated location.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98154c9f48190aeca779d97151759 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.