Triple
T16037372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Tedford |
E389002
|
entity |
| Predicate | tenureAsHeadCoachAtFresnoStateSecondStintStart |
P7574
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Jeff Tedford, tenureAsHeadCoachAtFresnoStateSecondStintStart, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenureAsHeadCoachAtFresnoStateSecondStintStart Context triple: [Jeff Tedford, tenureAsHeadCoachAtFresnoStateSecondStintStart, 2022]
-
A.
servedAsInterimHeadCoachYear
Indicates that an entity held the position of interim head coach for another entity during a specified year.
-
B.
hiredAsHeadCoachYear
chosen
Indicates the year in which an individual was hired to serve as the head coach of a team or organization.
-
C.
startTimeAsHeadCoachOfSanFrancisco49ers
Indicates the date and time when someone began their tenure as head coach of the San Francisco 49ers.
-
D.
beganHeadCoachingCareerWith
Indicates that an individual started their head coaching career with a specified team or organization.
-
E.
athleticDirectorTenureStart
Indicates the date or time when an individual begins serving as an athletic director for an organization or institution.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.