Triple
T14113223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 AFC Championship Game |
E339696
|
entity |
| Predicate | homeTeamRegularSeasonRecordVsTitans |
P49500
|
FINISHED |
| Object | 2–0 |
—
|
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: 2–0 | Statement: [1999 AFC Championship Game, homeTeamRegularSeasonRecordVsTitans, 2–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamRegularSeasonRecordVsTitans Context triple: [1999 AFC Championship Game, homeTeamRegularSeasonRecordVsTitans, 2–0]
-
A.
titansRecordEnteringGame
Indicates that the Titans team begins participation in a game, marking their official entry into the contest.
-
B.
awayTeamRegularSeasonRecord
Indicates the win-loss (and possibly tie) record that the away team has accumulated during the regular season.
-
C.
nflRecord
Indicates the win-loss-tie performance record a team or individual has accumulated in NFL competition.
-
D.
NLTeamRegularSeasonRecord
Indicates the win–loss (and often tie) performance record of a National League baseball team over a regular season.
-
E.
teamRecord
chosen
Indicates the recorded performance statistics (such as wins, losses, and ties) associated with a particular team over a defined period or 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.