Triple
T2272301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Mays |
E50686
|
entity |
| Predicate | threwNoHitter |
P31114
|
FINISHED |
| Object | 1917-08-30 |
—
|
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: 1917-08-30 | Statement: [Carl Mays, threwNoHitter, 1917-08-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threwNoHitter Context triple: [Carl Mays, threwNoHitter, 1917-08-30]
-
A.
noHitters
chosen
Indicates that a pitcher or team has completed a game without allowing the opposing team any hits.
-
B.
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).
-
C.
noHitterOpponent
Indicates that the specified opponent team or player was the team/player against whom a no-hitter was pitched.
-
D.
noHitterTeam
Indicates that a team was involved in a no-hitter game, typically as the team whose pitcher(s) allowed no hits.
-
E.
pitchedShutoutIn
Indicates that an individual (typically a pitcher) completed a game in a particular event or season without allowing the opposing team to score any runs.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc39c6ff0819081a07696f1c29990 |
completed | March 7, 2026, 6:20 a.m. |
| PD | Predicate disambiguation | batch_69abbdb7719081909143efa8f48df4e4 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.