Triple
T2590229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dawn Wall |
E58102
|
entity |
| Predicate | notablePitches |
P18729
|
FINISHED |
| Object | Pitches 14 and 15 are among the crux pitches |
—
|
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: Pitches 14 and 15 are among the crux pitches | Statement: [The Dawn Wall, notablePitches, Pitches 14 and 15 are among the crux pitches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePitches Context triple: [The Dawn Wall, notablePitches, Pitches 14 and 15 are among the crux pitches]
-
A.
notablePitch
chosen
Indicates that an entity is recognized for having a particularly significant or noteworthy pitch, offer, or proposal in a given context.
-
B.
notablePitcher
Indicates that the subject is recognized as a distinguished or prominent pitcher in the context of baseball.
-
C.
notableBatter
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
D.
numberOfPitches
Indicates the total count of pitches involved in a given event, performance, or musical segment.
-
E.
notableEventInning
Indicates the specific inning during which a notable or significant event occurred in a game.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3feb45c81909369a49c3990294a |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.