Triple
T24707029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League Golden Glove |
E611919
|
entity |
| Predicate | awardedForRole |
P106705
|
FINISHED |
| Object | goalkeeper performance |
—
|
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: goalkeeper performance | Statement: [Premier League Golden Glove, awardedForRole, goalkeeper performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForRole Context triple: [Premier League Golden Glove, awardedForRole, goalkeeper performance]
-
A.
hasAwarderRole
Indicates that an entity serves in the role or capacity of granting or conferring an award to another entity.
-
B.
hasAwardedRoleType
Indicates that an entity has been granted or assigned a role of a specified type as an award or honor.
-
C.
awardingOrganizationRole
Indicates that an entity holds a specific role or capacity within the organization that grants or confers an award.
-
D.
awardedFrom
Indicates that one entity has received an award, prize, or honor that originates from or is granted by another entity.
-
E.
holderAwardedFor
chosen
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:24 a.m.