Triple
T23723328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Providence Friars |
E586202
|
entity |
| Predicate | homeVenueBasketballLocation |
P150903
|
FINISHED |
| Object | downtown Providence, Rhode Island |
—
|
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: downtown Providence, Rhode Island | Statement: [Providence Friars, homeVenueBasketballLocation, downtown Providence, Rhode Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueBasketballLocation Context triple: [Providence Friars, homeVenueBasketballLocation, downtown Providence, Rhode Island]
-
A.
primaryBasketballArenaLocation
chosen
Indicates the main geographic location where a basketball team’s primary home arena is situated.
-
B.
homeBasketballArena
Indicates that a specified basketball arena serves as the home venue for a particular team or organization.
-
C.
secondaryBasketballVenue
Indicates that a location serves as an additional or backup venue for hosting basketball events, secondary to the primary basketball facility.
-
D.
homeVenueWomen'sBasketball
Indicates the location that serves as the primary home court for a women's basketball team.
-
E.
gameVenue
Indicates the location or facility where a game or match 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b912a7548190afcfa03dd9adc47e |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:06 p.m.