Triple
T6146987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Budenholzer |
E137101
|
entity |
| Predicate | headCoachStartWithAtlantaHawks |
P7106
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Mike Budenholzer, headCoachStartWithAtlantaHawks, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headCoachStartWithAtlantaHawks Context triple: [Mike Budenholzer, headCoachStartWithAtlantaHawks, 2013]
-
A.
headCoachTenureStartTeamAtlantaFalcons
Indicates the time point when an individual began their tenure as head coach of the Atlanta Falcons.
-
B.
endTimeAsHeadCoachOfAtlantaFalcons
Indicates the date and time when an individual’s tenure as head coach of the Atlanta Falcons comes to an end.
-
C.
NBAHeadCoachingDebutTeam
Indicates the team for which a person made their debut as a head coach in the NBA.
-
D.
headCoachFrom
Indicates that one entity serves as the head coach and originates from, or is affiliated with, the location or organization represented by the other entity.
-
E.
headCoachStartYear
chosen
Indicates the year in which an individual began serving as the head coach of a 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cdeeaa88190948d9db6eb2dbf46 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.