Triple
T2191523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 Chicago Bears season |
E49871
|
entity |
| Predicate | regularSeasonEnd |
P17000
|
FINISHED |
| Object | 1985-12 |
—
|
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: 1985-12 | Statement: [1985 Chicago Bears season, regularSeasonEnd, 1985-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonEnd Context triple: [1985 Chicago Bears season, regularSeasonEnd, 1985-12]
-
A.
regularSeasonSuspensionDate
Indicates the date on which a suspension takes effect or applies during the regular season.
-
B.
endSeason
chosen
Indicates the action or event of bringing a particular season, series, or period to a close.
-
C.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
D.
typicalEndSeason
Indicates the season in which something (such as an activity, event, or condition) usually or characteristically comes to an end.
-
E.
seasonCulminatesIn
Indicates that a particular season reaches its peak, conclusion, or defining outcome in the specified event or state.
- 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.