Triple
T605924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Heinsohn |
E11593
|
entity |
| Predicate | coachingEnd |
P14503
|
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: [Tom Heinsohn, coachingEnd, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachingEnd Context triple: [Tom Heinsohn, coachingEnd, 1978]
-
A.
coachingSpecialty
Indicates that a coach focuses on or is specialized in a particular area, topic, or type of coaching.
-
B.
coachingTreeIncludes
Indicates that one coach is part of, or derived from, another coach’s coaching lineage or mentorship hierarchy.
-
C.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
D.
officeEnded
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
E.
headCoachEnd
chosen
Indicates the point in time or event at which an entity’s role or tenure as a head coach 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df34abc8190a578c8c2ab3d28e4 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.