Triple
T2685618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jay Feely |
E57476
|
entity |
| Predicate | endOfProfessionalCareer |
P39575
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Jay Feely, endOfProfessionalCareer, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfProfessionalCareer Context triple: [Jay Feely, endOfProfessionalCareer, 2014]
-
A.
seniorCareerEnd
chosen
Indicates the point in time or event at which an entity’s senior-level career or professional activity comes to an end.
-
B.
endOfInternationalCareer
Indicates that an entity’s participation or involvement in international-level activities or competitions has concluded.
-
C.
postPlayingCareer
Indicates a relationship where something pertains to or occurs during an entity’s period after its playing career has ended.
-
D.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
E.
umpiringCareerEnd
Indicates the time or event at which an individual's career as an umpire comes to an end.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9ef2fe0819082bbe746ca682a7e |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.