Triple
T36476340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference (USHL) |
E898676
|
entity |
| Predicate | usedInSeasonFormat |
P117126
|
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: [Eastern Conference (USHL), usedInSeasonFormat, USHL regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSeasonFormat Context triple: [Eastern Conference (USHL), usedInSeasonFormat, USHL regular season]
-
A.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
B.
competesInSeasonalFormat
Indicates that an entity participates in a competition that is organized into recurring seasons or seasonal formats.
-
C.
seasonFormatIncludes
chosen
Indicates that a particular season uses or contains a specified format as part of its structure or presentation.
-
D.
hasUseSeason
Indicates the season or time of year during which something is intended or suitable to be used.
-
E.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 3, 2026, 4:10 p.m.