Triple
T31300172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teardrops on My Guitar |
E798193
|
entity |
| Predicate | labelMarketingVersion |
P172212
|
FINISHED |
| Object | pop radio remix |
—
|
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: pop radio remix | Statement: [Teardrops on My Guitar, labelMarketingVersion, pop radio remix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelMarketingVersion Context triple: [Teardrops on My Guitar, labelMarketingVersion, pop radio remix]
-
A.
labelMarketingPositioning
Indicates that an entity defines or assigns the marketing positioning (how something is presented or positioned in the market) for another entity.
-
B.
labelMarketingRole
Indicates that an entity is assigned or associated with a specific marketing-related role or function.
-
C.
labelMarketingFocus
Indicates that something is designated as the primary marketing focus or emphasis within a given context.
-
D.
labelForOriginalVersion
Indicates that something serves as the label or name assigned specifically to the original version of another entity.
-
E.
coveredVersionLabel
Indicates that one version’s label is included within or accounted for by another version in a coverage relationship.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
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:14 p.m.