Triple
T2810987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean McVay |
E54168
|
entity |
| Predicate | roleAtWashingtonRedskins |
P13665
|
FINISHED |
| Object | offensive coordinator |
—
|
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: offensive coordinator | Statement: [Sean McVay, roleAtWashingtonRedskins, offensive coordinator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtWashingtonRedskins Context triple: [Sean McVay, roleAtWashingtonRedskins, offensive coordinator]
-
A.
roleAtNewEnglandPatriots
Indicates the specific role, position, or capacity an entity holds within the New England Patriots organization.
-
B.
RedskinsDivision
Indicates that a team or entity is in the same competitive division as the Washington Redskins (now Washington Commanders) within a sports league.
-
C.
roleAtSportsTeam
chosen
Indicates the specific position or function an individual holds within a sports team.
-
D.
roleInFranchiseHistory
Indicates the specific function, position, or contribution an entity has within the historical development or timeline of a franchise.
-
E.
playedInNFCChampionshipGameWith
Indicates that two players participated together on the same team in at least one NFC Championship 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde335b38819090c70d5e2ca14d79 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.