Triple
T18300179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgeport Bluefish |
E438338
|
entity |
| Predicate | wonDivisionChampionship |
P10278
|
FINISHED |
| Object | 1998 |
—
|
LITERAL FINISHED |
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: 1998 | Statement: [Bridgeport Bluefish, wonDivisionChampionship, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonDivisionChampionship Context triple: [Bridgeport Bluefish, wonDivisionChampionship, 1998]
-
A.
wonDivisionTitle
chosen
Indicates that an entity secured first place in its competitive division, earning the division championship title.
-
B.
wonChallengeCup
Indicates that one entity emerged as the victor in a specific Challenge Cup competition or tournament against others.
-
C.
winningTeamDivision
Indicates the division to which the team that won a given game, match, or competition belongs.
-
D.
wonLeagueTitle
Indicates that a team or individual finished a competition as champions, securing the league title for that season or tournament.
-
E.
wonConferenceChampionshipsIn
Indicates that an entity has secured one or more conference championship titles in a specified league, sport, or time period.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017e88cc8190a969eb628ca1b496 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.