Triple
T25529146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total Request Live |
E639863
|
entity |
| Predicate | revivalRunStartDate |
P7739
|
FINISHED |
| Object | 2017-10-02 |
—
|
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: 2017-10-02 | Statement: [Total Request Live, revivalRunStartDate, 2017-10-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalRunStartDate Context triple: [Total Request Live, revivalRunStartDate, 2017-10-02]
-
A.
revivalRunStart
chosen
Indicates the point in time or event at which a revival process or renewed operation begins.
-
B.
revivalEndTime
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
C.
revivalYear
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
-
D.
revivalOriginalReleaseStart
Indicates the date or point in time when the original release associated with a later revival first began.
-
E.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f861fa088190a77a182aa602703e |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:13 p.m.