Triple
T13402255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Koharski |
E319859
|
entity |
| Predicate | retiredFromNHLOfficiating |
P2644
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Don Koharski, retiredFromNHLOfficiating, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromNHLOfficiating Context triple: [Don Koharski, retiredFromNHLOfficiating, 2009]
-
A.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
-
B.
retiredFrom
chosen
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
C.
retiredBy
Indicates that one entity has formally ended the active status, use, or service of another entity.
-
D.
retirementAsMLBUmpire
Indicates the event or state in which an individual ceases serving in the role of a Major League Baseball umpire.
-
E.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4982e0819087a9fcb2fa88541f |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.