Triple
T20603151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 MLB season |
E506232
|
entity |
| Predicate | worldSeriesGames |
P135997
|
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: [1984 MLB season, worldSeriesGames, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldSeriesGames Context triple: [1984 MLB season, worldSeriesGames, 5]
-
A.
WorldSeriesGames
Indicates a relationship where a game is identified as one of the games that make up a particular World Series.
-
B.
worldSeriesGameCount
chosen
Indicates the total number of games played in a particular World Series matchup.
-
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.
worldSeriesGamesHosted
Indicates that the subject has hosted one or more World Series baseball games, with the object specifying which games or how many were hosted.
-
E.
WorldSeriesGame5Completion
Indicates that the fifth game of a World Series has concluded, marking the completion of that specific game in the championship series.
- 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.