Triple
T2386065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voulez-Vous |
E48825
|
entity |
| Predicate | hasRhythmCharacteristic |
P7864
|
FINISHED |
| Object | energetic rhythm |
—
|
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: energetic rhythm | Statement: [Voulez-Vous, hasRhythmCharacteristic, energetic rhythm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRhythmCharacteristic Context triple: [Voulez-Vous, hasRhythmCharacteristic, energetic rhythm]
-
A.
hasRhythmicStyle
chosen
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
B.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
C.
hasBPMApprox
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
-
D.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
E.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7d9d8148190bb8aa16fd4364aba |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.