Triple
T1621897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019–20 NBA season |
E35049
|
entity |
| Predicate | regularSeasonStartDate |
P14544
|
FINISHED |
| Object | 2019-10-22 |
—
|
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: 2019-10-22 | Statement: [2019–20 NBA season, regularSeasonStartDate, 2019-10-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonStartDate Context triple: [2019–20 NBA season, regularSeasonStartDate, 2019-10-22]
-
A.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
B.
firstRegularSeasonGameDate
chosen
Indicates the calendar date on which an entity’s first regular-season game took place.
-
C.
regularSeasonWeeks
Indicates the number of weeks that make up the regular season portion of a schedule or competition.
-
D.
regularSeasonTitle
Indicates that a team or competitor won the championship or top standing for the regular season portion of a competition or league.
-
E.
openSeason
Indicates that a period has begun during which a particular activity (such as hunting, fishing, or competition) is officially allowed or actively underway.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.