Triple
T16498132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hash Pipe |
E400735
|
entity |
| Predicate | featuresHeavyDistortion |
P56451
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hash Pipe, featuresHeavyDistortion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHeavyDistortion Context triple: [Hash Pipe, featuresHeavyDistortion, yes]
-
A.
hasGuitarEffect
chosen
Indicates that one entity applies, uses, or is associated with a particular guitar effect in relation to another entity.
-
B.
hasHeavierSoundThan
Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of another entity.
-
C.
featuresDrumMachine
Indicates that something includes or makes use of a drum machine as part of its composition or functionality.
-
D.
notableInstrumentFeature
Indicates that an instrument is distinguished by a particular characteristic, quality, or component that is especially noteworthy or defining.
-
E.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e3505f48190a6891a5f29377212 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.