Triple
T10994762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Steel |
E259833
|
entity |
| Predicate | regularSeasonCompetition |
P25200
|
FINISHED |
| Object | USHL regular season |
—
|
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: USHL regular season | Statement: [Chicago Steel, regularSeasonCompetition, USHL regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonCompetition Context triple: [Chicago Steel, regularSeasonCompetition, USHL regular season]
-
A.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
B.
hasRegularSeason
chosen
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
C.
conferenceRegularSeasonChampionship
Indicates that a team has won the conference’s regular-season championship in a given sport or league.
-
D.
regularSeasonStart
Indicates the date or point in time when a competition’s regular season officially begins.
-
E.
regularSeasonTitle
Indicates that a team or competitor won the championship or top standing for the regular season portion of a competition or league.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d59ebc8190baff1f50bdc46c1b |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.