Triple
T30755240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonnies |
E783065
|
entity |
| Predicate | homeArenaForWomen'sBasketball |
P67406
|
FINISHED |
| Object | Reilly Center |
—
|
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: Reilly Center | Statement: [Bonnies, homeArenaForWomen'sBasketball, Reilly Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeArenaForWomen'sBasketball Context triple: [Bonnies, homeArenaForWomen'sBasketball, Reilly Center]
-
A.
homeVenueWomen'sBasketball
chosen
Indicates the location that serves as the primary home court for a women's basketball team.
-
B.
homeBasketballArena
Indicates that a specified basketball arena serves as the home venue for a particular team or organization.
-
C.
primaryBasketballArenaLocation
Indicates the main geographic location where a basketball team’s primary home arena is situated.
-
D.
homeVolleyballArena
Indicates that one entity serves as the primary or official volleyball arena or home court for the other entity.
-
E.
secondaryBasketballVenue
Indicates that a location serves as an additional or backup venue for hosting basketball events, secondary to the primary basketball facility.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f95b4f48190b1dcd818f4fdee15 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.