Triple
T37058224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shot |
E917251
|
entity |
| Predicate | opponentConference |
P84737
|
FINISHED |
| Object | Southeastern Conference |
—
|
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: Southeastern Conference | Statement: [The Shot, opponentConference, Southeastern Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentConference Context triple: [The Shot, opponentConference, Southeastern Conference]
-
A.
opponentTeamConference
chosen
Indicates the athletic conference to which the opposing team belongs in a given competition or matchup.
-
B.
rivalConferenceTeams
Indicates that the two teams compete in the same athletic conference and are considered rivals within that conference.
-
C.
leagueConference
Indicates that a sports league is associated with, organized into, or belongs to a particular conference within its competitive structure.
-
D.
athleticConferenceContext
Indicates the relationship between an entity and the athletic conference setting or framework within which it participates or is relevant.
-
E.
awayTeamConference
Indicates the athletic conference to which the away (visiting) team belongs in a sporting 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:14 p.m.