Triple
T12946128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Broyles |
E309770
|
entity |
| Predicate | athleticDirectorStart |
P101910
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Frank Broyles, athleticDirectorStart, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: athleticDirectorStart Context triple: [Frank Broyles, athleticDirectorStart, 1974]
-
A.
athleticDirector
Indicates that one entity serves as the athletic director (the person in charge of overseeing athletic programs) for another entity, such as a school or organization.
-
B.
athleticDirectorOf
Indicates that one entity serves as the athletic director (the chief administrator of athletic programs) for another entity, typically an institution or organization.
-
C.
athleticDirectorSchool
Indicates that a person serves as the athletic director for a particular school.
-
D.
athleticDirectorTenureStart
chosen
Indicates the date or time when an individual begins serving as an athletic director for an organization or institution.
-
E.
athleticDirectorOffice
Indicates that one entity is the office or workplace associated with the athletic director of another entity.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.