Triple
T35402092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebuilding Ball State football program |
E1023261
|
entity |
| Predicate | mainCoach |
P133649
|
FINISHED |
| Object | Brady Hoke |
—
|
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: Brady Hoke | Statement: [Rebuilding Ball State football program, mainCoach, Brady Hoke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCoach Context triple: [Rebuilding Ball State football program, mainCoach, Brady Hoke]
-
A.
coachSince
Indicates that one entity has been serving as a coach for another entity starting from a specified point in time.
-
B.
conferenceCoach
Indicates a person who provides guidance, training, or mentorship to participants in the context of a conference or similar professional gathering.
-
C.
isCoach
chosen
Indicates that one entity serves as the coach (trainer or instructor) of another entity.
-
D.
secondaryCoach
Indicates that an entity serves as an assistant or secondary coach in relation to a primary coach or coaching role.
-
E.
playingCoach
Indicates a person who simultaneously serves as both a player and a coach for the same team or organization.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:03 p.m.