Triple
T33246214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 AFC Championship Game |
E851107
|
entity |
| Predicate | teamFromAFCWest |
P168240
|
FINISHED |
| Object | Los Angeles Raiders |
—
|
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: Los Angeles Raiders | Statement: [1983 AFC Championship Game, teamFromAFCWest, Los Angeles Raiders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamFromAFCWest Context triple: [1983 AFC Championship Game, teamFromAFCWest, Los Angeles Raiders]
-
A.
teamFromWesternDivision
Indicates that a team belongs to or is associated with the Western Division within a league or organization.
-
B.
teamFromAFC
chosen
Indicates that a team competes in or is affiliated with the American Football Conference (AFC).
-
C.
cbaTeam
Indicates that one entity is a member of, or associated with, a specific CBA (Collective Bargaining Agreement) team.
-
D.
proBowlTeam
Indicates that a player was selected to and participated on a specific team in the Pro Bowl all-star game.
-
E.
americanFootballTeamOf
Indicates that one entity is the American football team associated with, representing, or belonging to another entity (such as a school, city, or organization).
- 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_69f6daf3963081909fc96cbd1642cd21 |
completed | May 3, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69f6d82fef788190b9ad19a36c0312dc |
completed | May 3, 2026, 5:08 a.m. |
Created at: May 1, 2026, 1:31 a.m.