Triple

T36738856
Position Surface form Disambiguated ID Type / Status
Subject King Tubby E907555 entity
Predicate significantTechnique P3047 FINISHED
Object use of reverb and echo in dub mixes 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: use of reverb and echo in dub mixes | Statement: [King Tubby, significantTechnique, use of reverb and echo in dub mixes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: significantTechnique
Context triple: [King Tubby, significantTechnique, use of reverb and echo in dub mixes]
  • A. featuresTechnique
    Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
  • B. significantSince
    Indicates that a relationship, condition, or status has held particular importance or relevance starting from a specified point in time.
  • C. allowedTechnique
    Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
  • D. usedByTechnique
    Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
  • E. hasTechnique chosen
    Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
  • 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_69f76e75aa6881909b844d00a3888ee5 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:12 p.m.