Triple
T20603146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 MLB season |
E506232
|
entity |
| Predicate | bestRegularSeasonRecordLosses |
P14131
|
FINISHED |
| Object | 58 |
—
|
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: 58 | Statement: [1984 MLB season, bestRegularSeasonRecordLosses, 58]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestRegularSeasonRecordLosses Context triple: [1984 MLB season, bestRegularSeasonRecordLosses, 58]
-
A.
losingTeamRegularSeasonRecord
Indicates the win-loss record that the losing team had during the regular season.
-
B.
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.
-
C.
regularSeasonLosses
Indicates the number of games a team lost during the regular season portion of a competition or league.
-
D.
seasonRecordLosses
chosen
Indicates the number of games a team lost during a specific season.
-
E.
bestRegularSeasonWins
Indicates the number of wins a team achieved in its most successful regular season.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa22663881909a8d4644e1c48dc2 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.