Triple
T31170460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ful Stop |
E794588
|
entity |
| Predicate | hasDrumPatternStyle |
P7864
|
FINISHED |
| Object | motorik-influenced |
—
|
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: motorik-influenced | Statement: [Ful Stop, hasDrumPatternStyle, motorik-influenced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrumPatternStyle Context triple: [Ful Stop, hasDrumPatternStyle, motorik-influenced]
-
A.
hasRhythmicStyle
chosen
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
B.
hasDrumProgrammingBy
Indicates that the drum programming for a work (such as a song or track) is created or performed by a specified entity.
-
C.
hasDrumProgramming
Indicates that one entity is responsible for creating, sequencing, or programming the drum parts used by another entity (such as a track, album, or performance).
-
D.
hasDrum
Indicates that an entity possesses or is equipped with a drum.
-
E.
hasDrumLoop
Indicates that an entity includes, uses, or is associated with a repeating drum pattern or drum loop.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:07 p.m.