Triple
T28564115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Valvano |
E722625
|
entity |
| Predicate | nicknameOfTeamCoached |
P164878
|
FINISHED |
| Object | Cardiac Pack |
—
|
NE NERFINISHED |
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: Cardiac Pack | Statement: [Jim Valvano, nicknameOfTeamCoached, Cardiac Pack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfTeamCoached Context triple: [Jim Valvano, nicknameOfTeamCoached, Cardiac Pack]
-
A.
headCoachTeam
Indicates that a person serves as the head coach of a particular team.
-
B.
teamCoachedFrom
Indicates that a coaching relationship exists where a coach is responsible for training or managing a team originating from a specific organization, location, or context.
-
C.
teamCoachedInChampionshipSeason
Indicates that a person served as the coach of a particular team during a season in which that team competed in a championship.
-
D.
coachOf
Indicates that one entity serves as the coach (trainer or manager) of another entity, typically a person or team.
-
E.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
- F. None of above. chosen
Provenance (4 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:06 a.m.