Triple
T5465891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Sharman |
E122707
|
entity |
| Predicate | ABAteamChampionshipCoached |
P7572
|
FINISHED |
| Object | Utah Stars 1971 |
—
|
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: Utah Stars 1971 | Statement: [Bill Sharman, ABAteamChampionshipCoached, Utah Stars 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ABAteamChampionshipCoached Context triple: [Bill Sharman, ABAteamChampionshipCoached, Utah Stars 1971]
-
A.
championshipWonAsCoach
chosen
Indicates that the subject, acting in the role of coach, has won a championship title with the associated team or organization.
-
B.
notableTeamCoached
Indicates that a person has served as a coach for a team that is considered notable or significant.
-
C.
notableAchievementAsCoach
Indicates that the subject has a significant or distinguished accomplishment specifically in their role as a coach.
-
D.
gamesCoachedWithTeam
Indicates the number of games a coach has led while associated with a specific team.
-
E.
workedUnderHeadCoach
Indicates that one person held a role or position under the authority or supervision of another person who was serving as the head coach.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.