Triple
T31314681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Belong With Me (Taylor’s Version) |
E798558
|
entity |
| Predicate | hasUpdatedRecording |
P172215
|
FINISHED |
| Object | vocals |
—
|
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: vocals | Statement: [You Belong With Me (Taylor’s Version), hasUpdatedRecording, vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpdatedRecording Context triple: [You Belong With Me (Taylor’s Version), hasUpdatedRecording, vocals]
-
A.
hasRe-recording
Indicates that one recording is a new or updated version made again from the same original material or performance.
-
B.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
C.
hasRecordingLegacy
Indicates that an entity is associated with a historical or prior version of a recording, capturing its legacy or earlier state.
-
D.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
E.
isReRecording
Indicates that an existing recording is being recorded again, typically to replace, update, or improve the original version.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 9:15 p.m.