Triple
T38678543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 Rose Bowl |
E943823
|
entity |
| Predicate | visitorTeamUniversity |
P191657
|
FINISHED |
| Object | Arizona State 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: Arizona State University | Statement: [1997 Rose Bowl, visitorTeamUniversity, Arizona State University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorTeamUniversity Context triple: [1997 Rose Bowl, visitorTeamUniversity, Arizona State University]
-
A.
homeTeamUniversity
Indicates that a specified university serves as the home institution or host team in a given game, match, or sporting event.
-
B.
losingTeamUniversity
Indicates that a university is the one whose team lost in a particular competition or game.
-
C.
teamInstitution
Indicates that a team is formally associated with, represents, or is part of a particular institution.
-
D.
universityTeamNumber
Indicates the numerical identifier assigned to a specific university team within a given context or competition.
-
E.
visitingTeamFranchise
Indicates that one franchise is the visiting (away) team in a particular game or matchup involving another franchise.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce54532948190a5cfacfe18e09322 |
completed | May 7, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:33 p.m.