Triple
T33660682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 NFC Championship Game |
E862342
|
entity |
| Predicate | homeTeamRunningBack |
P36657
|
FINISHED |
| Object | Joe Morris |
—
|
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: Joe Morris | Statement: [1986 NFC Championship Game, homeTeamRunningBack, Joe Morris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamRunningBack Context triple: [1986 NFC Championship Game, homeTeamRunningBack, Joe Morris]
-
A.
runningBack
chosen
Indicates that one entity is acting as a running back in relation to another entity, typically within the context of an American football play or team.
-
B.
notableRunningBackTeam2
Indicates that the second team is notably associated with a particular running back, such as being the team they are especially recognized for playing on.
-
C.
numberOfRunningBacks
Indicates the quantity of running backs involved or associated in the given context or situation.
-
D.
rushingYardsWithTeam
Indicates the number of rushing yards a player gained while playing for a specific team.
-
E.
awayTeamKicker
Indicates the player who serves as the kicker for the away team in a game or match.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa36f640819098051eff7e5a5787 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.