Triple
T12172322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Offensive Player of the Year |
E289999
|
entity |
| Predicate | individualOrTeamAward |
P16455
|
FINISHED |
| Object | individual |
—
|
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: individual | Statement: [Offensive Player of the Year, individualOrTeamAward, individual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: individualOrTeamAward Context triple: [Offensive Player of the Year, individualOrTeamAward, individual]
-
A.
isIndividualOrTeamAward
chosen
Indicates that an award is given either to a single individual or collectively to a team, rather than to another type of recipient.
-
B.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
C.
isSpecialAwardOf
Indicates that an award is a distinctive or exceptional honor specifically given to a particular entity (such as a person, work, or organization).
-
D.
awardOrRanking
Indicates that there is an award, honor, or ranking status conferred on or associated with an entity.
-
E.
awardTo
Indicates that an award, prize, or honor is given or assigned to a particular recipient.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.