Triple
T4964082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverfront Stadium |
E111476
|
entity |
| Predicate | hostedNoHitter |
P27014
|
FINISHED |
| Object | Tom Browning perfect game (1988-09-16) |
—
|
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: Tom Browning perfect game (1988-09-16) | Statement: [Riverfront Stadium, hostedNoHitter, Tom Browning perfect game (1988-09-16)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedNoHitter Context triple: [Riverfront Stadium, hostedNoHitter, Tom Browning perfect game (1988-09-16)]
-
A.
threwNoHitterFor
Indicates that a pitcher successfully completed a no-hitter game while playing for a specific team.
-
B.
noHitterOpponent
Indicates that the specified opponent team or player was the team/player against whom a no-hitter was pitched.
-
C.
noHitters
Indicates that a pitcher or team has completed a game without allowing the opposing team any hits.
-
D.
noHitterLocation
chosen
Indicates the location or venue where a no-hitter game occurred.
-
E.
noHitterTeam
Indicates that a team was involved in a no-hitter game, typically as the team whose pitcher(s) allowed no hits.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.