Triple
T34089910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corey Jae Crowder |
E874274
|
entity |
| Predicate | allNBAGLeagueTeam |
P178215
|
FINISHED |
| Object | NBA D-League All-Star (2014) |
—
|
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: NBA D-League All-Star (2014) | Statement: [Corey Jae Crowder, allNBAGLeagueTeam, NBA D-League All-Star (2014)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allNBAGLeagueTeam Context triple: [Corey Jae Crowder, allNBAGLeagueTeam, NBA D-League All-Star (2014)]
-
A.
allNBATeam
Indicates that an entity (typically a player) has been selected to an All-NBA Team for a given season or time period.
-
B.
NBAteam
Indicates that one entity is a professional basketball team that competes in the National Basketball Association (NBA) and the other entity is associated with it in that team role.
-
C.
basketballTeamOf
Indicates that one entity is the basketball team to which another entity belongs or is affiliated.
-
D.
preNBAClub
Indicates that a person was associated with a particular basketball club or team before joining the NBA.
-
E.
NBAChampionshipTeam
Indicates that a team has won the NBA championship title for a given season.
- F. None of above. chosen
Provenance (4 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:52 a.m.