Triple
T14893825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1956 World Series |
E359817
|
entity |
| Predicate | perfectGameStrikeouts |
P69101
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [1956 World Series, perfectGameStrikeouts, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perfectGameStrikeouts Context triple: [1956 World Series, perfectGameStrikeouts, 7]
-
A.
strikeoutsMLB
chosen
Indicates the number of times a pitcher retires batters by strikeout in Major League Baseball.
-
B.
strikeoutsLeader
Indicates that the subject is the player or entity leading others in the number of strikeouts over a specified period or context.
-
C.
strikeoutRate
Indicates the frequency or proportion at which a pitcher (or batter) records strikeouts relative to total opportunities.
-
D.
MVPStrikeouts
Indicates that the entity, as a Most Valuable Player (MVP), recorded a certain number of strikeouts.
-
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.
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_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. |
Created at: April 10, 2026, 2:10 a.m.