Triple
T30351364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn–Saint Joseph's basketball rivalry |
E772000
|
entity |
| Predicate | hasHomeArenaForSaintJosephs |
P48389
|
FINISHED |
| Object | Hagan Arena |
—
|
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: Hagan Arena | Statement: [Penn–Saint Joseph's basketball rivalry, hasHomeArenaForSaintJosephs, Hagan Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeArenaForSaintJosephs Context triple: [Penn–Saint Joseph's basketball rivalry, hasHomeArenaForSaintJosephs, Hagan Arena]
-
A.
cityOfChampionHomeArena
Indicates that a city is the home location of the arena where a champion’s team or individual competitor plays or competes.
-
B.
homeArenaOfChampionTeam
chosen
Indicates that a particular arena serves as the primary home venue for a specified champion team.
-
C.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
D.
hasSportsTeamVenueFor
Indicates that a venue serves as the home or hosting location for a particular sports team.
-
E.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 29, 2026, 7:56 p.m.