Triple
T7256023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1982–83 NBA season |
E157722
|
entity |
| Predicate | championRecordRegularSeason |
P11629
|
FINISHED |
| Object | 65–17 |
—
|
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: 65–17 | Statement: [1982–83 NBA season, championRecordRegularSeason, 65–17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championRecordRegularSeason Context triple: [1982–83 NBA season, championRecordRegularSeason, 65–17]
-
A.
championRegularSeasonRecord
chosen
Indicates that an entity is the champion associated with a particular regular season record.
-
B.
championRegularSeasonWins
Indicates that an entity is the champion based on having the highest number of regular season wins.
-
C.
championTeamRegularSeasonPlace
Indicates the final standing or rank that the championship-winning team achieved in the regular season before the playoffs or finals.
-
D.
runnerUpRegularSeasonRecord
Indicates the regular season performance record (such as wins and losses) of the team that finished as runner-up.
-
E.
hasChiefsRegularSeasonRecord
Indicates the regular-season win-loss-tie record of the Kansas City Chiefs associated with an entity (such as a coach, season, or player).
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eaa274bc8190b017b71583711453 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.