Triple
T9672087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasty Boys-era Reds |
E234052
|
entity |
| Predicate | worldSeriesResult1990 |
P14135
|
FINISHED |
| Object | 4–0 series victory |
—
|
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: 4–0 series victory | Statement: [Nasty Boys-era Reds, worldSeriesResult1990, 4–0 series victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldSeriesResult1990 Context triple: [Nasty Boys-era Reds, worldSeriesResult1990, 4–0 series victory]
-
A.
hits1919WorldSeries
Indicates a relationship where a player records a hit during the 1919 World Series.
-
B.
resultingWorldSeries
chosen
Indicates the specific World Series event or outcome that results from a given preceding condition, season, or set of circumstances.
-
C.
WorldSeriesTeam
Indicates that a team participated as one of the competing teams in a given World Series.
-
D.
GiantsWorldSeriesOutcome
Indicates the result or status of the San Francisco Giants’ performance in a given World Series.
-
E.
firstMLBGameResult
Indicates the outcome of an entity’s first game played in Major League Baseball, such as whether it was a win, loss, or other recorded result.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6aa01c819083fc758470096ec2 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.