Triple
T8087345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Golden |
E188765
|
entity |
| Predicate | roleAtNotreDame |
P38510
|
FINISHED |
| Object | defensive 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: defensive coordinator | Statement: [Al Golden, roleAtNotreDame, defensive coordinator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtNotreDame Context triple: [Al Golden, roleAtNotreDame, defensive coordinator]
-
A.
roleAtUCSD
Indicates that an entity holds or has held a specific role or position at the University of California, San Diego (UCSD).
-
B.
campusRole
Indicates the specific position, function, or capacity an individual holds within a campus or academic institution.
-
C.
roleAtInstitution
chosen
Indicates that an entity holds or has held a specific role or position within a particular institution.
-
D.
notableStudentBodyAssociatedWith
Indicates that there is a significant or noteworthy group of students associated with a particular entity, such as an institution, organization, or program.
-
E.
positionOfNotableAlumnus
Indicates the professional role or office held by a notable alumnus in relation to an institution or organization.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4162244481908ab1202a9974deaa |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.