Triple
T2811913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Coast Hockey League |
E54189
|
entity |
| Predicate | playoffTiming |
P31045
|
FINISHED |
| Object | typically April to June |
—
|
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: typically April to June | Statement: [East Coast Hockey League, playoffTiming, typically April to June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffTiming Context triple: [East Coast Hockey League, playoffTiming, typically April to June]
-
A.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
B.
playoffStructure
Indicates how a competition’s postseason phase is organized, including the format, seeding, and progression of teams or players through playoff rounds.
-
C.
playoffsStartDate
chosen
Indicates the calendar date on which a competition’s playoff phase begins.
-
D.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
E.
playoffPath
Indicates the sequence of games, rounds, or matchups a team or player must progress through in a playoff tournament.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde354a5881908cd3d545f7dda81c |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.