Triple
T37284474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Larsen's perfect game |
E925492
|
entity |
| Predicate | secondBaseUmpire |
P200358
|
FINISHED |
| Object | Tom Gorman |
—
|
NE NERFINISHED |
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: Tom Gorman | Statement: [Don Larsen's perfect game, secondBaseUmpire, Tom Gorman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondBaseUmpire Context triple: [Don Larsen's perfect game, secondBaseUmpire, Tom Gorman]
-
A.
thirdBaseUmpire
Indicates that the subject serves as the umpire positioned at third base in a baseball game, responsible for making calls on plays occurring near that base.
-
B.
secondBaseman
Indicates that an entity plays the defensive position of second baseman in baseball relative to a team or game.
-
C.
rightFieldUmpire
Indicates that the subject is serving as the umpire positioned in right field in relation to the object (typically a game or play).
-
D.
eraAsUmpire
Indicates the time period during which an entity served in the role of an umpire.
-
E.
leftFieldUmpire
Indicates that an entity serves as the umpire positioned in the left field area relative to a particular game or play.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:16 p.m.