Triple
T8027565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020–21 NHL season |
E186892
|
entity |
| Predicate | playFormat |
P29019
|
FINISHED |
| Object | intra-divisional play in regular season |
—
|
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: intra-divisional play in regular season | Statement: [2020–21 NHL season, playFormat, intra-divisional play in regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playFormat Context triple: [2020–21 NHL season, playFormat, intra-divisional play in regular season]
-
A.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
B.
tracksFormat
Indicates that one entity records or follows the specific structure, style, or configuration defined by another entity.
-
C.
playType
chosen
Indicates the specific category or style of play or performance associated with an event or action.
-
D.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
-
E.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eccacb0819082f7c3d6fd48e3c4 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.