Triple
T7417259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball pitcher |
E171160
|
entity |
| Predicate | batsAgainst |
P76840
|
FINISHED |
| Object | opposing batters |
—
|
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: opposing batters | Statement: [Major League Baseball pitcher, batsAgainst, opposing batters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batsAgainst Context triple: [Major League Baseball pitcher, batsAgainst, opposing batters]
-
A.
battingAverageAgainst
Indicates the average batting performance (e.g., hits per at-bat) that a batter achieves specifically against a particular pitcher, team, or category of opponents.
-
B.
winnerBats
Indicates that the entity identified as the winner performs the action of batting.
-
C.
battingAggression
Indicates how aggressively a batter attempts to score runs, typically reflected in risk-taking and attacking shot selection.
-
D.
bats
Indicates that one entity hits or strikes another entity, typically using a bat or similar implement.
-
E.
battingStrength
Indicates the relative power or effectiveness of an entity’s batting performance in a given context.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c7ae0c8190a8348d6223aeeecc |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1c3307481909a7f6bb69d4fddac |
completed | March 27, 2026, 9:08 p.m. |
Created at: March 27, 2026, 3:11 p.m.