Triple
T36538741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hi-NRG |
E900657
|
entity |
| Predicate | usesRhythmPattern |
P179371
|
FINISHED |
| Object | four-on-the-floor 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: four-on-the-floor beat | Statement: [Hi-NRG, usesRhythmPattern, four-on-the-floor beat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRhythmPattern Context triple: [Hi-NRG, usesRhythmPattern, four-on-the-floor beat]
-
A.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
B.
hasRhythmicComplexity
Indicates that one entity exhibits or involves a level of rhythmic intricacy or variation in relation to another entity or context.
-
C.
hasRhythmInfluence
Indicates that one entity has influenced or shaped the rhythmic patterns, style, or timing characteristics of another entity.
-
D.
usesBeatType
chosen
Indicates that an entity employs or is based on a particular type or pattern of beat (rhythmic structure).
-
E.
hasRhythmicOrigin
Indicates that something originates from, is derived from, or is fundamentally based on rhythm or rhythmic patterns.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:11 p.m.