Triple
T31315243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don’t You (Taylor’s Version) (From The Vault) |
E798575
|
entity |
| Predicate | hasLeadInstruments |
P128335
|
FINISHED |
| Object | piano |
—
|
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: piano | Statement: [Don’t You (Taylor’s Version) (From The Vault), hasLeadInstruments, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadInstruments Context triple: [Don’t You (Taylor’s Version) (From The Vault), hasLeadInstruments, piano]
-
A.
includesInstruments
Indicates that one entity contains, involves, or makes use of one or more instruments as part of its composition or execution.
-
B.
typicalLeadInstrument
chosen
Indicates that an instrument is commonly used as the primary or lead instrument in a given musical context or performance.
-
C.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
D.
hasMainInstrumentalElements
Indicates that one entity includes or is characterized by the primary instrumental components or parts of another entity.
-
E.
usesInstrumentsOnStage
Indicates that an entity performs on stage while making use of musical instruments.
- 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_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 29, 2026, 9:15 p.m.