Triple
T34692301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock Purdy |
E890931
|
entity |
| Predicate | tookOverAsStarterSeason |
P38865
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Brock Purdy, tookOverAsStarterSeason, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOverAsStarterSeason Context triple: [Brock Purdy, tookOverAsStarterSeason, 2022]
-
A.
originalSeasonStart
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
B.
startSeason
Indicates the point in time or event at which a particular season begins.
-
C.
seasonDebut
Indicates the event or time at which an entity (such as a person, show, or team) first appears or begins participating in a particular season.
-
D.
becameStartingQuarterbackSeason
chosen
Indicates that an individual assumed the role of starting quarterback for a team beginning with a specified season.
-
E.
beganInLeagueSeason
Indicates that an entity (such as a team, player, or competition) began its participation or activity during a specified league season.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7235395488190b246679f9ee8c508 |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.