Triple
T19128574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League 1882 season |
E468251
|
entity |
| Predicate | championWinLossRecord |
P134518
|
FINISHED |
| Object | 55–29 |
—
|
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: 55–29 | Statement: [National League 1882 season, championWinLossRecord, 55–29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championWinLossRecord Context triple: [National League 1882 season, championWinLossRecord, 55–29]
-
A.
championWins
Indicates that a champion emerges victorious in a competition, match, or contest.
-
B.
championRegularSeasonWins
Indicates that an entity is the champion based on having the highest number of regular season wins.
-
C.
championFinalsRecord
Indicates the win–loss record a champion has specifically in finals appearances.
-
D.
championshipWinRate
Indicates the proportion of championships won relative to the total number of championship opportunities or appearances.
-
E.
championTotalWinsIncludingPostseason
Indicates the total number of games a champion has won in a season, counting both regular season and postseason victories.
- F. None of above. chosen
Provenance (4 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ceb5808190b3b53d9e8df3605a |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.