Triple
T31192584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockshow |
E795220
|
entity |
| Predicate | restoredVersionReleaseYear |
P171354
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Rockshow, restoredVersionReleaseYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredVersionReleaseYear Context triple: [Rockshow, restoredVersionReleaseYear, 2013]
-
A.
restoredVersionRelease
Indicates that one version is the restored or recovered release of another version, typically after rollback, recovery, or repair.
-
B.
remasterReleaseYear
Indicates the year in which a remastered version of an existing work was released.
-
C.
remakeReleaseYear
Indicates the year in which a remake of an original work was released.
-
D.
recoveredYear
Indicates the year in which something that was lost, damaged, or unwell was successfully restored, retrieved, or brought back to a desired state.
-
E.
restorationPremieredAt
Indicates that a particular restoration of a work had its first public showing or debut at a specific event, venue, or location.
- F. None of above. chosen
Provenance (4 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:08 p.m.