Triple
T6082016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reggie Miller |
E135544
|
entity |
| Predicate | retiredJerseyYear |
P19406
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Reggie Miller, retiredJerseyYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredJerseyYear Context triple: [Reggie Miller, retiredJerseyYear, 2006]
-
A.
dateOfJerseyRetirement
chosen
Indicates the date on which a team officially retired an athlete’s jersey number.
-
B.
retirementYearAsPlayer
Indicates the year in which an individual ended their career as an active player.
-
C.
retiredJerseyCollege
Indicates that a college has formally retired a particular jersey number, typically in honor of a former player or coach associated with that institution.
-
D.
wearsNumberRetiredBy
Indicates that one entity wears a jersey number that has been officially retired in honor of another entity.
-
E.
jerseyRetiredLeagueWide
Indicates that a player's jersey number has been officially retired across an entire league, preventing any team in that league from issuing it again.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05774bc948190a446b27e83f7079b |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.