Triple
T38263228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Hockey Association playoffs |
E1017982
|
entity |
| Predicate | playoffRoundsInclude |
P8299
|
FINISHED |
| Object | quarterfinals |
—
|
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: quarterfinals | Statement: [World Hockey Association playoffs, playoffRoundsInclude, quarterfinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffRoundsInclude Context triple: [World Hockey Association playoffs, playoffRoundsInclude, quarterfinals]
-
A.
playoffRound
chosen
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
B.
playoffRoundNumber
Indicates the specific stage or round within a playoff series in which an event, game, or matchup occurs.
-
C.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
D.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.