Triple
T16881768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New Style |
E421433
|
entity |
| Predicate | featuresVocalTrading |
P124831
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The New Style, featuresVocalTrading, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresVocalTrading Context triple: [The New Style, featuresVocalTrading, yes]
-
A.
featuresVocalHarmonyBy
Indicates that the subject work includes vocal harmony performances contributed by the specified artist or group.
-
B.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
C.
featuresVocoder
Indicates that one entity includes or provides a vocoder as a functional component or feature of another entity.
-
D.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
E.
featuresVocalEnsemble
Indicates that something includes or presents a group of vocal performers singing together.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7fc61a08190b9f611c06a95be01 |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32e2c07b081908c8fee9f5507bb9e |
completed | April 18, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:29 a.m.