Triple
T27005664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Scott |
E680233
|
entity |
| Predicate | noHitterSignificance |
P161767
|
FINISHED |
| Object | Clinched 1986 NL West title for Houston Astros |
—
|
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: Clinched 1986 NL West title for Houston Astros | Statement: [Mike Scott, noHitterSignificance, Clinched 1986 NL West title for Houston Astros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noHitterSignificance Context triple: [Mike Scott, noHitterSignificance, Clinched 1986 NL West title for Houston Astros]
-
A.
noHitterCount
Indicates the number of no-hitters a pitcher (or team) has recorded.
-
B.
noHitters
Indicates that a pitcher or team has completed a game without allowing the opposing team any hits.
-
C.
noHitterResult
Indicates that a baseball game concluded as a no-hitter, specifying the outcome of that no-hitter performance.
-
D.
threwNoHitterAtLevel
Indicates that one entity pitched a no-hitter game at a specified competitive level or league.
-
E.
threwNoHitterFor
Indicates that a pitcher successfully completed a no-hitter game while playing for a specific 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d139f081909f9ca04e04095dba |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 7 a.m.