Triple
T31429834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys 1990s Super Bowl dynasty |
E801764
|
entity |
| Predicate | keyTightEnd |
P126826
|
FINISHED |
| Object | Jay Novacek |
—
|
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: Jay Novacek | Statement: [Dallas Cowboys 1990s Super Bowl dynasty, keyTightEnd, Jay Novacek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyTightEnd Context triple: [Dallas Cowboys 1990s Super Bowl dynasty, keyTightEnd, Jay Novacek]
-
A.
startingTightEnd
Indicates that an entity serves as the primary tight end at the start of a game, play, season, or lineup configuration.
-
B.
isKeyPlayerFor
chosen
Indicates that an entity plays a crucial or central role in the success, functioning, or performance of another entity (such as a team, project, or organization).
-
C.
decisiveTouchdownScorer
Indicates the player who scored the touchdown that ultimately determined the outcome of the game.
-
D.
awayTeamKicker
Indicates the player who serves as the kicker for the away team in a game or match.
-
E.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:56 p.m.