Triple
T36925170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Joseph Holovak |
E913320
|
entity |
| Predicate | coachingTitle |
P108878
|
FINISHED |
| Object | head coach |
—
|
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: head coach | Statement: [Michael Joseph Holovak, coachingTitle, head coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachingTitle Context triple: [Michael Joseph Holovak, coachingTitle, head coach]
-
A.
coachedToTitle
Indicates that one entity served as a coach for another entity that went on to win a championship or title under their guidance.
-
B.
coachTitle
chosen
Indicates the formal title or designation held by a coach in relation to a team, organization, or role.
-
C.
coachingAt
Indicates that one entity is serving as a coach at, or providing coaching services within, a particular organization, institution, or location.
-
D.
coachingSpecialty
Indicates that a coach focuses on or is specialized in a particular area, topic, or type of coaching.
-
E.
coachingBase
Indicates a foundational coaching relationship in which one entity serves as the primary coach or mentor for another.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.