Triple
T14893823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1956 World Series |
E359817
|
entity |
| Predicate | perfectGameHitsAllowed |
P116560
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [1956 World Series, perfectGameHitsAllowed, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perfectGameHitsAllowed Context triple: [1956 World Series, perfectGameHitsAllowed, 0]
-
A.
perfectGameVenue
Indicates that a perfect game was achieved at the specified venue.
-
B.
game6CompleteGameShutoutPitcher
Indicates that the pitcher threw a complete game in game 6 without allowing the opposing team to score any runs.
-
C.
strikeoutsMLB
Indicates the number of times a pitcher retires batters by strikeout in Major League Baseball.
-
D.
ballsAndStrikes
Indicates the relationship between a pitch and how it is judged in baseball as either a ball or a strike.
-
E.
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).
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f9d10c819091732d7a5a42a682 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:10 a.m.