Triple
T273662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Scherzer |
E5199
|
entity |
| Predicate | throwsPitchType |
P2172
|
FINISHED |
| Object | four-seam fastball |
—
|
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: four-seam fastball | Statement: [Max Scherzer, throwsPitchType, four-seam fastball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throwsPitchType Context triple: [Max Scherzer, throwsPitchType, four-seam fastball]
-
A.
throws
chosen
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
B.
usesPitchClock
Indicates that an entity employs or is governed by a pitch clock to regulate the timing of pitches.
-
C.
notablePitcher
Indicates that the subject is recognized as a distinguished or prominent pitcher in the context of baseball.
-
D.
ballType
Indicates the specific category or kind of ball associated with an entity.
-
E.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dd0a99c819089968a5400c58c5f |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.