Triple
T9535923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1928 World Series |
E230013
|
entity |
| Predicate | CardinalsRegularSeasonRecord |
P10319
|
FINISHED |
| Object | 95–59 |
—
|
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: 95–59 | Statement: [1928 World Series, CardinalsRegularSeasonRecord, 95–59]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CardinalsRegularSeasonRecord Context triple: [1928 World Series, CardinalsRegularSeasonRecord, 95–59]
-
A.
EaglesRegularSeasonRecord
Indicates the win-loss (and possibly tie) performance of the Eagles during a specific regular season.
-
B.
CubsRegularSeasonRecord
Indicates the relationship that specifies the Chicago Cubs’ win–loss (and possibly tie) record for a particular regular baseball season.
-
C.
GiantsRegularSeasonRecordEnteringGame
Indicates the Giants’ cumulative regular-season win–loss record at the time a particular game begins.
-
D.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
E.
NLTeamRegularSeasonRecord
chosen
Indicates the win–loss (and often tie) performance record of a National League baseball team over a 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98cd6a5c8190835c0910ec38ede3 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.