Triple
T6657840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 MLB strike |
E151392
|
entity |
| Predicate | postseasonAffected |
P25201
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [1985 MLB strike, postseasonAffected, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postseasonAffected Context triple: [1985 MLB strike, postseasonAffected, no]
-
A.
hasPostseasonImpact
chosen
Indicates that an event, action, or outcome has a direct effect on postseason qualification, seeding, or performance.
-
B.
hasPostseasonEvent
Indicates that an entity is associated with or participates in a postseason event, such as playoffs or championships, following a regular season.
-
C.
postseasonPeriod
Indicates that a time span occurs during the postseason phase of a sports or competitive season, after the regular season has concluded.
-
D.
postseasonGamesPlayed
Indicates the number of games an entity has participated in during postseason or playoff competition.
-
E.
postseasonEnd
Indicates the point in time or event at which a sports league’s postseason (playoffs) concludes.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.