Triple
T69099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Hockey League |
E1381
|
entity |
| Predicate | playoffFormat |
P2673
|
FINISHED |
| Object | best-of-seven series |
—
|
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: best-of-seven series | Statement: [National Hockey League, playoffFormat, best-of-seven series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffFormat Context triple: [National Hockey League, playoffFormat, best-of-seven series]
-
A.
playoffName
Indicates the designated name or title assigned to a specific playoff series, round, or event within a competition.
-
B.
postseasonType
Indicates the specific kind of postseason competition or phase associated with an event or team.
-
C.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
D.
playoffFieldSizeHistory
Indicates the historical sizes of the playoff field, showing how many participants qualified for the playoffs in different seasons or time periods.
-
E.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea8cfd081908a26edad2473dde3 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.