Triple
T16034661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrian Peterson |
E388937
|
entity |
| Predicate | comebackSeason |
P94430
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Adrian Peterson, comebackSeason, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comebackSeason Context triple: [Adrian Peterson, comebackSeason, 2012]
-
A.
madeComeback
chosen
Indicates that an entity returned to a previous level of success, performance, or prominence after a period of decline, absence, or setback.
-
B.
attemptedComebackSeason
Indicates that an entity made an effort to return to a previous level of performance or prominence after a period of decline or absence.
-
C.
comebackAlbumFor
Indicates that one album serves as an artist’s return or resurgence release following a period of inactivity, decline, or absence.
-
D.
comebackSingleFor
Indicates that a particular single serves as a comeback release for an artist or group, marking their return after a hiatus or previous work.
-
E.
comebackContext
Indicates the situational background, circumstances, or prior events that frame or motivate a comeback or return.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.