Triple
T38482961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canisius Golden Griffins men's basketball |
E917832
|
entity |
| Predicate | homeConferenceLeague |
P119343
|
FINISHED |
| Object | MAAC |
—
|
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: MAAC | Statement: [Canisius Golden Griffins men's basketball, homeConferenceLeague, MAAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeConferenceLeague Context triple: [Canisius Golden Griffins men's basketball, homeConferenceLeague, MAAC]
-
A.
homeLeague
Indicates that a sports team primarily competes in, or is officially associated with, a particular league as its main organizational affiliation.
-
B.
homeConferenceForBasketball
chosen
Indicates that a particular athletic conference is the primary or official conference affiliation for a given basketball team.
-
C.
homeConferenceChampionshipVenue
Indicates the venue where a team’s home conference championship game is held.
-
D.
homeLeagueOf
Indicates that a league is the primary or official league in which a team or club regularly competes.
-
E.
hostLeague
Indicates that one entity serves as the organizing league or governing competition framework for another entity, such as a team or event.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.