Triple
T18129969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dennis Martínez |
E433982
|
entity |
| Predicate | numberOfPerfectGamesPitched |
P130565
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Dennis Martínez, numberOfPerfectGamesPitched, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPerfectGamesPitched Context triple: [Dennis Martínez, numberOfPerfectGamesPitched, 1]
-
A.
threwPerfectGame
Indicates that one entity (typically a pitcher) completed a game without allowing any opposing player to reach base, achieving a perfect game against another entity (typically a team).
-
B.
yearOfPerfectGame
Indicates the specific year in which a perfect game occurred or was achieved.
-
C.
perfectGameInnings
Indicates that the referenced innings constitute a perfect game, where no opposing batter successfully reaches base.
-
D.
pitchedPerfectGameDate
Indicates the date on which a pitcher threw a perfect game.
-
E.
perfectGameRunsAllowed
Indicates that in a perfect game, the number of runs allowed by the pitcher or team is recorded or constrained to a specific value (typically zero).
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddf11a74819094e8fe8dae4615bb |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:29 a.m.