Triple
T4211965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Hockey League |
E93921
|
entity |
| Predicate | playoffDuration |
P8177
|
FINISHED |
| Object | approximately March to May |
—
|
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: approximately March to May | Statement: [Western Hockey League, playoffDuration, approximately March to May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffDuration Context triple: [Western Hockey League, playoffDuration, approximately March to May]
-
A.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
B.
seasonDuration
chosen
Indicates the length of time that a particular season lasts.
-
C.
playoffStructure
Indicates how a competition’s postseason phase is organized, including the format, seeding, and progression of teams or players through playoff rounds.
-
D.
playoffPoints
Indicates the number of points an entity has earned or been credited with in playoff or postseason competition.
-
E.
playoffMeetingsCount
Indicates the number of times the entities have faced each other in 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.