Triple
T1327854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1972 MLB strike |
E28370
|
entity |
| Predicate | regularSeasonGamesCanceled |
P27248
|
FINISHED |
| Object | 86 |
—
|
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: 86 | Statement: [1972 MLB strike, regularSeasonGamesCanceled, 86]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonGamesCanceled Context triple: [1972 MLB strike, regularSeasonGamesCanceled, 86]
-
A.
regularSeasonGamesPerTeam
Indicates the number of games each team plays during the regular season.
-
B.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
C.
postseasonGamesPlayed
Indicates the number of games an entity has participated in during postseason or playoff competition.
-
D.
hasRegularSeasonGamesAgainst
Indicates that one team or participant plays scheduled, recurring competitive games against another during the regular season.
-
E.
numberOfGamesScheduled
Indicates the total count of games that have been planned or arranged for a given entity or time period.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.