Triple
T33246241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 AFC Championship Game |
E851107
|
entity |
| Predicate | regularSeasonMeetingWinner |
P193670
|
FINISHED |
| Object | Seattle Seahawks |
—
|
NE NERFINISHED |
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: Seattle Seahawks | Statement: [1983 AFC Championship Game, regularSeasonMeetingWinner, Seattle Seahawks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonMeetingWinner Context triple: [1983 AFC Championship Game, regularSeasonMeetingWinner, Seattle Seahawks]
-
A.
postseasonMeetingSeason
Indicates that the entities are connected through a postseason meeting that took place in a specific sports season.
-
B.
conferenceRegularSeasonChampionship
Indicates that a team has won the conference’s regular-season championship in a given sport or league.
-
C.
championshipGameSeason
Indicates the specific sports season during which a particular championship game took place.
-
D.
conferenceRegularSeasonChampionships
Indicates the number of times an entity has won its conference’s regular-season championship.
-
E.
postseasonSeriesWinner
Indicates which competitor or team won a particular postseason series in a sports or competitive context.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 1, 2026, 1:31 a.m.