Triple
T21181120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulham Player of the Season |
E521951
|
entity |
| Predicate | voteBasis |
P13230
|
FINISHED |
| Object | performances during the season |
—
|
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: performances during the season | Statement: [Fulham Player of the Season, voteBasis, performances during the season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteBasis Context triple: [Fulham Player of the Season, voteBasis, performances during the season]
-
A.
votingBasis
chosen
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
B.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
C.
votePattern
Indicates a recurring way or tendency in how an entity casts votes across issues, candidates, or time.
-
D.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
E.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301da0ac8190a965fee7b6d845e7 |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:01 p.m.