Triple
T16037376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Tedford |
E389002
|
entity |
| Predicate | roleAtBoiseState |
P38510
|
FINISHED |
| Object | offensive coordinator |
—
|
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: offensive coordinator | Statement: [Jeff Tedford, roleAtBoiseState, offensive coordinator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBoiseState Context triple: [Jeff Tedford, roleAtBoiseState, offensive coordinator]
-
A.
campusRole
Indicates the specific position, function, or capacity an individual holds within a campus or academic institution.
-
B.
roleAtUCSD
Indicates that an entity holds or has held a specific role or position at the University of California, San Diego (UCSD).
-
C.
roleAtInstitution
chosen
Indicates that an entity holds or has held a specific role or position within a particular institution.
-
D.
alumniRole
Indicates that an entity holds or held a specific role, position, or capacity as an alumnus/alumna of another entity (such as an institution or program).
-
E.
courseRole
Indicates the specific function or position an individual holds within a course, such as student, instructor, or assistant.
- 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.