Triple
T33246236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 AFC Championship Game |
E851107
|
entity |
| Predicate | visitingTeamSeed |
P18175
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [1983 AFC Championship Game, visitingTeamSeed, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitingTeamSeed Context triple: [1983 AFC Championship Game, visitingTeamSeed, 4]
-
A.
visitingTeamConferenceSeed
Indicates the ranking or seed assigned to the visiting team within its conference for a given competition or season.
-
B.
homeTeamSeed
Indicates the ranking or seed assigned to the home team within a tournament or competition bracket.
-
C.
losingTeamSeed
Indicates the tournament seed or ranking assigned to the team that lost in a given game or matchup.
-
D.
visitingTeamRecordEnteringGame
Indicates the performance record (such as wins and losses) that the visiting team has accumulated prior to the start of the game.
-
E.
playoffSeed
chosen
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:31 a.m.