Triple
T33221569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992–93 NBA season |
E850433
|
entity |
| Predicate | regularSeasonBestRecordLosses |
P14874
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [1992–93 NBA season, regularSeasonBestRecordLosses, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonBestRecordLosses Context triple: [1992–93 NBA season, regularSeasonBestRecordLosses, 20]
-
A.
losingTeamRegularSeasonRecord
Indicates the win-loss record that the losing team had during the regular season.
-
B.
regularSeasonLosses
chosen
Indicates the number of games a team lost during the regular season portion of a competition or league.
-
C.
seasonRecordLosses
Indicates the number of games a team lost during a specific season.
-
D.
bestRegularSeasonRecord
Indicates that an entity (typically a team) achieved the highest overall performance record during the regular season compared to all others in the same competition.
-
E.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:30 a.m.