Triple
T36451411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Faurot |
E898019
|
entity |
| Predicate | tenureAsAthleticDirectorStartYear |
P101910
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Don Faurot, tenureAsAthleticDirectorStartYear, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenureAsAthleticDirectorStartYear Context triple: [Don Faurot, tenureAsAthleticDirectorStartYear, 1935]
-
A.
athleticDirectorTenureStart
chosen
Indicates the date or time when an individual begins serving as an athletic director for an organization or institution.
-
B.
athleticDirectorYears
Indicates the span of years during which an individual served as an athletic director.
-
C.
athleticDirectorOf
Indicates that one entity serves as the athletic director (the chief administrator of athletic programs) for another entity, typically an institution or organization.
-
D.
headCoachStartYear
Indicates the year in which an individual began serving as the head coach of a team or organization.
-
E.
tenureAsGeneralManagerStart
Indicates the date or time when an individual begins their tenure serving as a general manager.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.