Triple
T539112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1950 World Series |
E12389
|
entity |
| Predicate | YankeesRegularSeasonRecord |
P15124
|
FINISHED |
| Object | 98–56 |
—
|
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: 98–56 | Statement: [1950 World Series, YankeesRegularSeasonRecord, 98–56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: YankeesRegularSeasonRecord Context triple: [1950 World Series, YankeesRegularSeasonRecord, 98–56]
-
A.
BrooklynFranchiseWorldSeriesAppearancesToDate
Indicates the number of times the Brooklyn franchise has appeared in the World Series up to the present date.
-
B.
GiantsRegularSeasonRecordEnteringGame
Indicates the Giants’ cumulative regular-season win–loss record at the time a particular game begins.
-
C.
AmericanLeagueEastTitle
Indicates that a team has won the American League East division championship in a given baseball season.
-
D.
YankeesRunsSeventhInning
Indicates the number of runs scored by the Yankees in the seventh inning of a game.
-
E.
YankeesStatusEnteringGame
chosen
Indicates the competitive or situational status of the Yankees (such as record, streak, or standing) immediately before a specific game begins.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.