Triple
T15647539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Shula |
E376219
|
entity |
| Predicate | offensiveCoordinatorTenureStart |
P119592
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Mike Shula, offensiveCoordinatorTenureStart, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveCoordinatorTenureStart Context triple: [Mike Shula, offensiveCoordinatorTenureStart, 1996]
-
A.
offensiveCoordinatorAtStart
Indicates that the person served as the offensive coordinator of a team at the beginning of a specified season or time period.
-
B.
nflHeadCoachDebutSeason
Indicates the season in which a person first served as a head coach in the NFL.
-
C.
beganNFLHeadCoachingCareerWith
Indicates that an individual's first position as an NFL head coach was with the specified team.
-
D.
headCoachStartYear
Indicates the year in which an individual began serving as the head coach of a team or organization.
-
E.
startTimeAsDefensiveCoordinatorForSeattleSeahawks
Indicates the date and time when an individual began serving as the defensive coordinator for the Seattle Seahawks.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed5b8b081908d7127964eed3b09 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.