Triple
T23641663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheila Ki Jawani |
E583911
|
entity |
| Predicate | basedOnRhythmStyle |
P7864
|
FINISHED |
| Object | up-tempo dance beat |
—
|
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: up-tempo dance beat | Statement: [Sheila Ki Jawani, basedOnRhythmStyle, up-tempo dance beat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnRhythmStyle Context triple: [Sheila Ki Jawani, basedOnRhythmStyle, up-tempo dance beat]
-
A.
hasRhythmicStyle
chosen
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
B.
hasRhythmOrigin
Indicates that one rhythm, style, or rhythmic pattern originates from, is derived from, or has its roots in another source.
-
C.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
-
D.
hasRhythmicOrigin
Indicates that something originates from, is derived from, or is fundamentally based on rhythm or rhythmic patterns.
-
E.
percussionStyle
Indicates the specific manner or technique in which percussion is played or executed in a given context.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28152108190972ac680cba986d7 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.