Triple
T33213149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019–20 NBA G League season |
E850212
|
entity |
| Predicate | MostImprovedPlayerTeam |
P71110
|
FINISHED |
| Object | Delaware Blue Coats |
—
|
NE NERFINISHED |
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: Delaware Blue Coats | Statement: [2019–20 NBA G League season, MostImprovedPlayerTeam, Delaware Blue Coats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MostImprovedPlayerTeam Context triple: [2019–20 NBA G League season, MostImprovedPlayerTeam, Delaware Blue Coats]
-
A.
mostImprovedPlayerTeam
chosen
Indicates that a player was recognized as the most improved player while playing for a particular team.
-
B.
ManagerOfTheYearTeam
Indicates that a person was recognized as the Manager of the Year for a specific team.
-
C.
MVPawardTeam
Indicates that a team received the Most Valuable Player (MVP) award in a given context or competition.
-
D.
OffensivePlayerOfTheYearTeam
Indicates that a player who received an Offensive Player of the Year award was a member of the specified team during the season for which the award was given.
-
E.
mostAwardsHolderTeam
Indicates the team that holds the highest number of awards within a given set or competition.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:30 a.m.