Triple
T22665453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2010–11 |
E559770
|
entity |
| Predicate | mostAssists |
P109157
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Premier League 2010–11, mostAssists, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostAssists Context triple: [Premier League 2010–11, mostAssists, 14]
-
A.
mostAssistsNumber
chosen
Indicates that an entity holds the highest number of assists recorded within a given context or comparison set.
-
B.
mostAssistsPlayer
Indicates that the subject is the player who recorded the highest number of assists for the referenced game, season, team, or context.
-
C.
assistsLeaderTeam
Indicates that an entity provides help or support to the leader’s team in carrying out its activities or responsibilities.
-
D.
MVPAssists
Indicates that one entity, recognized as the most valuable player (MVP), provides assistance or support to another entity in achieving a goal or outcome.
-
E.
topAssistsAssistsPerGame
Indicates that the subject ranks among the top performers in terms of average assists made per game.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781b3dbc8190a312843cf8c1bfc6 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.