Triple
T36898091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griffons |
E911949
|
entity |
| Predicate | basketballHomeCourt |
P791
|
FINISHED |
| Object | MWSU Fieldhouse |
—
|
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: MWSU Fieldhouse | Statement: [Griffons, basketballHomeCourt, MWSU Fieldhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basketballHomeCourt Context triple: [Griffons, basketballHomeCourt, MWSU Fieldhouse]
-
A.
playsHomeBasketballAt
Indicates that a person or team plays their home basketball games at a specified venue or location.
-
B.
homeBasketballArena
chosen
Indicates that a specified basketball arena serves as the home venue for a particular team or organization.
-
C.
usesStandardBasketballCourt
Indicates that the subject conducts its basketball-related activities on a regulation-size, standard-layout basketball court.
-
D.
homeCourtDedicatedTo
Indicates that a particular sports venue or court is officially named for or ceremonially assigned in honor of a specific person, group, or 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd927e2c8190ae0b48443bdea664 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.