Triple
T33213156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019–20 NBA G League season |
E850212
|
entity |
| Predicate | playoffsCanceled |
P27977
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [2019–20 NBA G League season, playoffsCanceled, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffsCanceled Context triple: [2019–20 NBA G League season, playoffsCanceled, yes]
-
A.
postseasonCanceled
chosen
Indicates that a planned postseason (playoff or tournament phase) was not held because it was canceled.
-
B.
seasonCancelled
Indicates that a planned season of events, episodes, or activities has been officially terminated and will not take place as scheduled.
-
C.
regularSeasonGamesCanceled
Indicates that scheduled regular-season games were canceled and did not take place as originally planned.
-
D.
playoffsStatus
Indicates the current stage or outcome of an entity’s participation in a playoff competition (e.g., qualified, in progress, eliminated, or champion).
-
E.
playoffContext
Indicates that the relationship or action occurs within the setting or circumstances of a playoff or postseason 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.