Triple
T13737381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub Crazy |
E329983
|
entity |
| Predicate | hasBeatCharacteristic |
P69783
|
FINISHED |
| Object | boom bap |
—
|
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: boom bap | Statement: [Sub Crazy, hasBeatCharacteristic, boom bap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeatCharacteristic Context triple: [Sub Crazy, hasBeatCharacteristic, boom bap]
-
A.
hasBeat
Indicates that one entity has defeated or surpassed another in a competitive or comparative context.
-
B.
beatCharacteristic
chosen
Indicates a characteristic or quality that defines or describes a particular beat (such as its style, pattern, or rhythmic property).
-
C.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
D.
hasMusicCharacteristic
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
E.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0204d50c8190a5413cc9a1b26e14 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.