Triple
T25046000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1960 Pittsburgh Pirates season |
E627242
|
entity |
| Predicate | WorldSeriesGame7FinalScore |
P126706
|
FINISHED |
| Object | 10–9 Pirates |
—
|
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: 10–9 Pirates | Statement: [1960 Pittsburgh Pirates season, WorldSeriesGame7FinalScore, 10–9 Pirates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WorldSeriesGame7FinalScore Context triple: [1960 Pittsburgh Pirates season, WorldSeriesGame7FinalScore, 10–9 Pirates]
-
A.
worldSeriesGame7FinalScore
chosen
Indicates the final score outcome of the decisive Game 7 in a World Series matchup between two teams.
-
B.
WorldSeriesGame5Completion
Indicates that the fifth game of a World Series has concluded, marking the completion of that specific game in the championship series.
-
C.
perfectGameFinalScore
Indicates that a game concluded as a perfect game and specifies the final score achieved.
-
D.
WorldSeriesGames
Indicates a relationship where a game is identified as one of the games that make up a particular World Series.
-
E.
worldSeriesClinchingGame
Indicates the game in a World Series that results in one team securing the championship title.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:08 a.m.