Triple
T29311129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Beatles remastered catalogue |
E743235
|
entity |
| Predicate | remasteringProjectStartYear |
P166831
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [The Beatles remastered catalogue, remasteringProjectStartYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remasteringProjectStartYear Context triple: [The Beatles remastered catalogue, remasteringProjectStartYear, 2005]
-
A.
remasterReleaseYear
Indicates the year in which a remastered version of an existing work was released.
-
B.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
-
C.
restorationPremieredAt
Indicates that a particular restoration of a work had its first public showing or debut at a specific event, venue, or location.
-
D.
firstCompleteStudioRecordingYear
Indicates the year in which an entity’s first complete studio recording was made.
-
E.
remixReleaseYear
Indicates the year in which a particular remix version of a work was released.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665e5ade481908eac1b24726ba5b5 |
completed | May 2, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1:16 p.m.