Triple
T21720395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stambaugh Stadium |
E536138
|
entity |
| Predicate | hasAthleticOffices |
P145086
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Stambaugh Stadium, hasAthleticOffices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAthleticOffices Context triple: [Stambaugh Stadium, hasAthleticOffices, yes]
-
A.
athleticDirectorOffice
Indicates that one entity is the office or workplace associated with the athletic director of another entity.
-
B.
universityAthleticDepartment
Indicates that a university has an associated athletic department that manages its sports programs and related activities.
-
C.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
D.
hasSportsDepartment
Indicates that an entity includes or maintains a department dedicated to sports-related activities or programs.
-
E.
hasAthleticProgramType
Indicates that an institution’s athletic program belongs to or is classified under a specific type or category of athletic program.
- F. None of above. chosen
Provenance (4 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96de818819084c268d4775a8e3a |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:47 p.m.