Triple
T11456086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shane Doan |
E271529
|
entity |
| Predicate | jerseyRetirementNumber |
P78159
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [Shane Doan, jerseyRetirementNumber, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyRetirementNumber Context triple: [Shane Doan, jerseyRetirementNumber, 19]
-
A.
jerseyNumber
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
B.
hasJerseyNumberRetired
chosen
Indicates that an entity has had its jersey number officially retired, typically in recognition of its contributions or achievements.
-
C.
dateOfJerseyRetirement
Indicates the date on which a team officially retired an athlete’s jersey number.
-
D.
retiredJerseyNumberByTeam
Indicates that a sports team has officially retired a specific jersey number in honor of a player or figure, making it unavailable for future use by team members.
-
E.
jerseyNumberRetiredInHisHonor
Indicates that a person’s jersey number has been officially retired by a team or organization as a tribute to that person’s contributions or legacy.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.