Triple
T11554811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Player of the Week awards |
E273989
|
entity |
| Predicate | isNonPlayoffAward |
P30668
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NBA Player of the Week awards, isNonPlayoffAward, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonPlayoffAward Context triple: [NBA Player of the Week awards, isNonPlayoffAward, true]
-
A.
isPostseasonAward
Indicates that an award is specifically given in recognition of performance during a postseason or playoff period, rather than the regular season.
-
B.
regularSeasonAward
chosen
Indicates that an entity received or is associated with an award specifically given for performance during the regular season of a competition or league.
-
C.
isNonPlayingAward
Indicates that an award is given for contributions not involving active participation in the game or performance itself.
-
D.
ABAPlayoffsMVP
Indicates that the subject was selected as the Most Valuable Player of the American Basketball Association (ABA) playoffs.
-
E.
playoffsMVPtrophy
Indicates that an entity is the Most Valuable Player trophy awarded for performance in the playoffs.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a86be308190973fea5d7db8ba9d |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.