Triple
T27543253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link Up & Suede |
E695292
|
entity |
| Predicate | isReleaseByDuo |
P46169
|
FINISHED |
| Object | NxWorries |
—
|
NE NERFINISHED |
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: NxWorries | Statement: [Link Up & Suede, isReleaseByDuo, NxWorries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReleaseByDuo Context triple: [Link Up & Suede, isReleaseByDuo, NxWorries]
-
A.
isSoloReleaseOf
Indicates that a release is a solo work attributed to a single primary artist, rather than a group or collaboration, for a given musical entity.
-
B.
isDoubleSong
Indicates that one song is a duplicate or alternate version of another song, such as a second take, remix, or re-recording.
-
C.
isDoubleCoverOf
Indicates that one object serves as a two-to-one covering of another, such that each point or element of the second is covered by exactly two corresponding points or elements of the first.
-
D.
associatedWithDuo
chosen
Indicates a relationship in which an entity is linked or connected to a specific duo, typically implying involvement, collaboration, or relevance to that pair.
-
E.
pairedReleaseWith
Indicates that two items are released together as a coordinated or associated pair.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 1:32 p.m.