Triple
T5046885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trent Dilfer |
E113687
|
entity |
| Predicate | roleInSuperBowlWin |
P14498
|
FINISHED |
| Object | starting quarterback |
—
|
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: starting quarterback | Statement: [Trent Dilfer, roleInSuperBowlWin, starting quarterback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSuperBowlWin Context triple: [Trent Dilfer, roleInSuperBowlWin, starting quarterback]
-
A.
SuperBowlChampionAsPlayerWith
Indicates that one entity was a Super Bowl champion as a player in association with the other entity (such as a team, season, or organization).
-
B.
wonSuperBowlWith
Indicates that one entity (typically a player, coach, or team member) achieved a Super Bowl victory while being part of a specific team.
-
C.
appearedInSuperBowl
chosen
Indicates that the entity participated as a player, coach, or key contributor in at least one Super Bowl game.
-
D.
superBowlChampionWith
Indicates that one entity is the Super Bowl champion associated with the other entity (such as a specific season, year, or team).
-
E.
SuperBowlWin
Indicates that a team has won the Super Bowl in a given season or game.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd740002b48190bc7aa176d734c589 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.