Triple
T2191524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 Chicago Bears season |
E49871
|
entity |
| Predicate | postseasonStart |
P31045
|
FINISHED |
| Object | 1986-01 |
—
|
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: 1986-01 | Statement: [1985 Chicago Bears season, postseasonStart, 1986-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postseasonStart Context triple: [1985 Chicago Bears season, postseasonStart, 1986-01]
-
A.
postseasonPeriod
Indicates that a time span occurs during the postseason phase of a sports or competitive season, after the regular season has concluded.
-
B.
playoffsStartDate
chosen
Indicates the calendar date on which a competition’s playoff phase begins.
-
C.
postseasonType
Indicates the specific kind of postseason competition or phase associated with an event or team.
-
D.
postseasonSeries
Indicates that there is a multi-game playoff or postseason competition series taking place between entities (typically teams) within a sports or competitive context.
-
E.
postseasonGamesPlayed
Indicates the number of games an entity has participated in during postseason or playoff competition.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf3f5e008190beda3ce5d77209e0 |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.