Triple
T27543255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link Up & Suede |
E695292
|
entity |
| Predicate | includesSingingBy |
P184004
|
FINISHED |
| Object | Anderson .Paak |
—
|
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: Anderson .Paak | Statement: [Link Up & Suede, includesSingingBy, Anderson .Paak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSingingBy Context triple: [Link Up & Suede, includesSingingBy, Anderson .Paak]
-
A.
hasSinging
chosen
Indicates that an entity performs, possesses, or is engaged in the action or activity of singing.
-
B.
includesScratchVocalsFrom
Indicates that one audio recording or track contains scratch (temporary or demo) vocal parts taken from another recording or session.
-
C.
hasSingingVoiceType
Indicates the specific category or classification of a person's singing voice (such as soprano, tenor, etc.) in relation to that person.
-
D.
singsWith
Indicates that two or more entities perform singing together, jointly participating in a vocal musical activity.
-
E.
isSpokenOrSung
Indicates that something (such as text, lyrics, or dialogue) is produced vocally, either by speaking or by singing.
- 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_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 27, 2026, 1:32 p.m.