Triple
T25562021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rootsman Skanking |
E640736
|
entity |
| Predicate | hasBassCharacteristic |
P44121
|
FINISHED |
| Object | heavy |
—
|
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: heavy | Statement: [Rootsman Skanking, hasBassCharacteristic, heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBassCharacteristic Context triple: [Rootsman Skanking, hasBassCharacteristic, heavy]
-
A.
hasBassIntroBy
Indicates a relationship where a musical piece features an introductory section performed or led by a bass instrument or bass player.
-
B.
hasMusicCharacteristic
chosen
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
C.
hasBassStringMaterial
Indicates that an entity’s bass strings are made of a specified material.
-
D.
hasNotableBassline
Indicates that something (typically a piece of music) features a bassline that is particularly prominent, distinctive, or otherwise noteworthy.
-
E.
hasBassist
Indicates that an entity (typically a musical group or band) has another entity serving in the role of its bassist.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 3:46 p.m.