Triple
T12172333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Offensive Player of the Year |
E289999
|
entity |
| Predicate | isTeamAchievement |
P13110
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Offensive Player of the Year, isTeamAchievement, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTeamAchievement Context triple: [Offensive Player of the Year, isTeamAchievement, false]
-
A.
teamAchievement
chosen
Indicates that a group of individuals collectively accomplished a shared goal or met a performance milestone.
-
B.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
C.
hostedTeamAchievement
Indicates that an entity organized or hosted an event or context in which a team achieved a particular accomplishment.
-
D.
isTeamConstruct
Indicates that an entity is a constructed or assembled team, rather than a naturally occurring or default group.
-
E.
isLifetimeAchievementType
Indicates that an award, honor, or recognition is of the lifetime achievement type, typically granted for sustained contributions over an extended period rather than for a single work or event.
- 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.