Triple
T2291485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1975 World Series |
E51512
|
entity |
| Predicate | game6FamousMoment |
P25528
|
FINISHED |
| Object | Carlton Fisk home run |
—
|
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: Carlton Fisk home run | Statement: [1975 World Series, game6FamousMoment, Carlton Fisk home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: game6FamousMoment Context triple: [1975 World Series, game6FamousMoment, Carlton Fisk home run]
-
A.
notableFootballEvent
Indicates an event in football that is distinguished by particular significance, impact, or memorability within the sport.
-
B.
famousMatch
Indicates that two entities are linked by a match or pairing that is widely known or celebrated.
-
C.
notablePlay
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
D.
seriesWinningGame
Indicates that a particular game is the decisive or clinching game in which one side wins the overall series.
-
E.
famousForEvent
chosen
Indicates that an entity is widely known or recognized specifically because of a particular event.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:48 p.m.