Triple
T14854415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Next to Me" music video |
E349313
|
entity |
| Predicate | featuresGenrePerformance |
P5483
|
FINISHED |
| Object | soul vocal performance |
—
|
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: soul vocal performance | Statement: ["Next to Me" music video, featuresGenrePerformance, soul vocal performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGenrePerformance Context triple: ["Next to Me" music video, featuresGenrePerformance, soul vocal performance]
-
A.
genreFeatures
chosen
Indicates that a particular genre is characterized or defined by certain features or attributes.
-
B.
featuresPerformerType
Indicates that something includes or highlights a performer of a specified type (e.g., musician, actor, or other performance role).
-
C.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
-
D.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
E.
genreSpecialty
Indicates that an entity specializes in or is particularly associated with a specific genre.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44318f0819080b6c599f2d3474f |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.