Triple
T26341770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Havlicek |
E662664
|
entity |
| Predicate | playedProfessionalYearsEnd |
P150011
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [John Havlicek, playedProfessionalYearsEnd, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedProfessionalYearsEnd Context triple: [John Havlicek, playedProfessionalYearsEnd, 1978]
-
A.
activeYearsInCareer
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
-
B.
playedProfessionalUntil
chosen
Indicates that an entity participated in a professional-level activity or career up to and including a specified end time or date.
-
C.
activeYearsInSport
Indicates the span of years during which an entity actively participated in a particular sport.
-
D.
professionalPlayingCareerEnd
Indicates the point in time when an individual's professional playing career comes to an end.
-
E.
playedCareerStartYear
Indicates the calendar year in which an entity’s playing career (such as a professional or competitive role) began.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 26, 2026, 10:39 p.m.