Triple
T9793829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 World Series |
E237668
|
entity |
| Predicate | gamesWithOneRunMargin |
P89997
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [1991 World Series, gamesWithOneRunMargin, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamesWithOneRunMargin Context triple: [1991 World Series, gamesWithOneRunMargin, 5]
-
A.
HomeRunDerbyTitles
Indicates the number of Home Run Derby titles an entity has won in competitive baseball home run hitting contests.
-
B.
averageMarginOfVictory
Indicates the typical point or score difference by which one competitor or team wins over opponents across a set of contests or games.
-
C.
WorldSeriesGamesLost
Indicates the number of World Series games that a team has lost in a given World Series or across World Series appearances.
-
D.
RunsBattedIn
Indicates the number of runs a batter causes to score as a direct result of their plate appearance or action.
-
E.
seriesWinningRunScoredBy
Indicates that a particular run, scored by a specific player, was the decisive run that clinched a series victory for that player’s team.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda347b6bc8190a99b7dec1650cd46 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:28 p.m.