Triple
T1668618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League Manager of the Month |
E36071
|
entity |
| Predicate | publicVoteWeight |
P29728
|
FINISHED |
| Object | 10% |
—
|
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: 10% | Statement: [Premier League Manager of the Month, publicVoteWeight, 10%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicVoteWeight Context triple: [Premier League Manager of the Month, publicVoteWeight, 10%]
-
A.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
B.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
C.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
D.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
E.
popularVoteRole
Indicates the role or capacity in which an entity participates in or is associated with a popular vote.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9178d84008190a96c1429420fb374 |
completed | March 5, 2026, 5:41 a.m. |
Created at: March 4, 2026, 7:29 p.m.