Triple
T13714903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977 World Series |
E328870
|
entity |
| Predicate | game6HomeRunsOffDifferentPitchersByReggieJackson |
P111291
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1977 World Series, game6HomeRunsOffDifferentPitchersByReggieJackson, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: game6HomeRunsOffDifferentPitchersByReggieJackson Context triple: [1977 World Series, game6HomeRunsOffDifferentPitchersByReggieJackson, 3]
-
A.
firstWorldSeriesHomeRunByAPitcherGame
Indicates that the event is the game in which a pitcher hit the first home run in World Series history.
-
B.
pitcherFacedForFirstHomeRun
Indicates the pitcher who was on the mound when a batter hit their first career home run.
-
C.
firstWorldSeriesHomeRunByAPitcher
Indicates that the referenced event is the first instance in World Series history where a pitcher hit a home run.
-
D.
opponentBatterInFamousHomeRun
Indicates that the subject was the opposing batter involved in a specific, well-known home run event.
-
E.
game6WinningPitcher
Indicates the pitcher who was credited with the win in game 6 of a series or matchup.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43973cf08190a417d0cca9dd314a |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.