Triple
T28870593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randy Edsall |
E732129
|
entity |
| Predicate | collegePlayerAt |
P27011
|
FINISHED |
| Object | Syracuse University |
—
|
NE NERFINISHED |
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: Syracuse University | Statement: [Randy Edsall, collegePlayerAt, Syracuse University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collegePlayerAt Context triple: [Randy Edsall, collegePlayerAt, Syracuse University]
-
A.
collegeAthleteIn
Indicates that an individual is an athlete who competes for or represents a particular college or university.
-
B.
leagueDuringCollege
Indicates the sports league or competitive organization in which an individual participated while they were in college.
-
C.
playedForCollegeTeamUntil
Indicates that an individual was a member of and played for a specific college team up to (and including) a particular end date or season.
-
D.
playedCollegeSport
chosen
Indicates that the subject participated in an organized college-level sport for the object institution.
-
E.
playedForCollegeTeamFrom
Indicates that an individual was a member of and played for a specific college team starting in a given year.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 28, 2026, 7:32 a.m.