Triple
T7094947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Johnson |
E165299
|
entity |
| Predicate | collegePlayerOfTheYearSeason |
P29583
|
FINISHED |
| Object | 1990–91 |
—
|
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: 1990–91 | Statement: [Larry Johnson, collegePlayerOfTheYearSeason, 1990–91]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collegePlayerOfTheYearSeason Context triple: [Larry Johnson, collegePlayerOfTheYearSeason, 1990–91]
-
A.
NaismithCollegePlayerOfTheYearInSeason
chosen
Indicates that a college basketball player was selected as the Naismith College Player of the Year for a specific season.
-
B.
FinalsMVPSeason
Indicates the season in which a player was awarded the Finals Most Valuable Player (MVP) honor.
-
C.
leagueRookieOfTheYearSeason
Indicates that an entity was selected as the league's Rookie of the Year for a particular season.
-
D.
Pac12PlayerOfTheYear
Indicates that the subject was selected as the Pac-12 Conference Player of the Year in a given season.
-
E.
teammateOfTheYear
Indicates that one entity has been recognized or awarded as the outstanding or most valuable teammate in relation to another entity or within a shared team context.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5530f2081908ac969ddfa7e9b5a |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.