Triple
T7542411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Diamondbacks–Los Angeles Dodgers rivalry |
E178310
|
entity |
| Predicate | hasHitByPitchIncidents |
P77905
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Arizona Diamondbacks–Los Angeles Dodgers rivalry, hasHitByPitchIncidents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHitByPitchIncidents Context triple: [Arizona Diamondbacks–Los Angeles Dodgers rivalry, hasHitByPitchIncidents, true]
-
A.
ledLeagueInHitByPitch
Indicates that the subject led a league in the number of times they were hit by a pitch during a given season or period.
-
B.
strikeoutsMLB
Indicates the number of times a pitcher retires batters by strikeout in Major League Baseball.
-
C.
hitsInMLB
Indicates the number of successful base hits a player has recorded in Major League Baseball games.
-
D.
hasPitchType
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
-
E.
numberOfPitches
Indicates the total count of pitches involved in a given event, performance, or musical segment.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8762b048190a0b262f9cb3fe1b0 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:48 p.m.