Triple
T11689193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Harmon |
E277823
|
entity |
| Predicate | collegeTeamNumberRetired |
P78159
|
FINISHED |
| Object | 98 |
—
|
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: 98 | Statement: [Tom Harmon, collegeTeamNumberRetired, 98]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collegeTeamNumberRetired Context triple: [Tom Harmon, collegeTeamNumberRetired, 98]
-
A.
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.
-
B.
leagueRetiredNumberBy
Indicates that a sports league has officially retired a specific jersey number in honor of a particular person or entity.
-
C.
nbaTeamNumberRetiredBy
Indicates that a specific jersey number has been officially retired by a particular NBA team in honor of a player or significant contribution.
-
D.
hasJerseyNumberRetired
chosen
Indicates that an entity has had its jersey number officially retired, typically in recognition of its contributions or achievements.
-
E.
collegeTeamNumber
Indicates the identifying number assigned to a college sports team.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a478f4c481908b2ba7b70972590d |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.