Triple
T7462554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HockeyAllsvenskan |
E176285
|
entity |
| Predicate | hasRegularSeasonStandings |
P11178
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [HockeyAllsvenskan, hasRegularSeasonStandings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularSeasonStandings Context triple: [HockeyAllsvenskan, hasRegularSeasonStandings, true]
-
A.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
B.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
C.
hasStandings
chosen
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
-
D.
hasRegularSeasonCoverage
Indicates that an entity provides media or broadcast coverage of another entity’s regular season events or games.
-
E.
hasPostseasonAccess
Indicates that an entity is granted the right or eligibility to participate in postseason or playoff competitions.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d80ae08190ba383066cf0cb2ce |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.