Triple
T2121415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Bender |
E43930
|
entity |
| Predicate | knownForPitch |
P7082
|
FINISHED |
| Object | sweeping curveball |
—
|
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: sweeping curveball | Statement: [Chief Bender, knownForPitch, sweeping curveball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForPitch Context triple: [Chief Bender, knownForPitch, sweeping curveball]
-
A.
notablePitch
Indicates that an entity is recognized for having a particularly significant or noteworthy pitch, offer, or proposal in a given context.
-
B.
knownForSports
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
C.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
-
D.
inningsPitched
Indicates the number of innings a pitcher has completed while actively pitching in a game or season.
-
E.
notablePitcher
chosen
Indicates that the subject is recognized as a distinguished or prominent pitcher in the context of baseball.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb51e8088190a1aeafee4e8dff63 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.