Triple
T31315817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run (Taylor’s Version) (From the Vault) |
E798592
|
entity |
| Predicate | originalRecordingDateEra |
P202673
|
FINISHED |
| Object | early 2010s |
—
|
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: early 2010s | Statement: [Run (Taylor’s Version) (From the Vault), originalRecordingDateEra, early 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRecordingDateEra Context triple: [Run (Taylor’s Version) (From the Vault), originalRecordingDateEra, early 2010s]
-
A.
originalRecordingEra
chosen
Indicates the historical time period during which the original recording was made.
-
B.
recordingEra
Indicates the historical time period or era during which the recording was made.
-
C.
recordingFormatEra
Indicates the historical time period or era associated with the recording format used for an audio or video recording.
-
D.
primaryEraOfRecordingsReissued
Indicates that the associated recordings being reissued predominantly originate from a particular historical or stylistic era.
-
E.
reRecordingEra
Indicates that one recording is a new or updated version created in a later era relative to an earlier recording.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
Created at: April 29, 2026, 9:15 p.m.