Triple
T1842474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL regular season |
E41205
|
entity |
| Predicate | hasStandingsBy |
P11178
|
FINISHED |
| Object | division |
—
|
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: division | Statement: [NHL regular season, hasStandingsBy, division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandingsBy Context triple: [NHL regular season, hasStandingsBy, division]
-
A.
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.
-
B.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
C.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
D.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
E.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.