Triple
T34365250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WaveIQ |
E881989
|
entity |
| Predicate | typicalFeatureOfWork |
P188879
|
FINISHED |
| Object | rhythmic grooves |
—
|
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: rhythmic grooves | Statement: [WaveIQ, typicalFeatureOfWork, rhythmic grooves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFeatureOfWork Context triple: [WaveIQ, typicalFeatureOfWork, rhythmic grooves]
-
A.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
B.
notableFeatureOfWork
Indicates that a particular feature, characteristic, or aspect is a notable or distinguishing element of a given work.
-
C.
creativeWorkCharacteristic
chosen
Indicates a relationship where a specific characteristic, feature, or attribute is associated with a creative work.
-
D.
featuresWorkType
Indicates that an entity includes, supports, or is characterized by a particular type or category of work.
-
E.
workOftenDepicts
Indicates that one entity’s work frequently portrays, represents, or includes the other entity as a subject or theme.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.