Triple

T23546440
Position Surface form Disambiguated ID Type / Status
Subject "I'm a Hustla" E577906 entity
Predicate featuresDistinctiveElement P68011 FINISHED
Object chopped-vocal beat 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: chopped-vocal beat | Statement: ["I'm a Hustla", featuresDistinctiveElement, chopped-vocal beat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: featuresDistinctiveElement
Context triple: ["I'm a Hustla", featuresDistinctiveElement, chopped-vocal beat]
  • A. featuresSign
    Indicates that an entity includes, displays, or incorporates a particular sign as part of its appearance, content, or design.
  • B. featuresIn
    Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
  • C. featuredElement chosen
    Indicates that one element is highlighted or given special prominence relative to others in a given context.
  • D. featuresRecurringElement
    Indicates that something includes an element, motif, or component that appears repeatedly over time or across multiple instances.
  • E. featuresElementSystem
    Indicates that a system includes or incorporates a particular element as one of its constituent parts or components.
  • 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_69e245f9d5d08190a4a20004e1784e20 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1aecb567c8190a54d2c3b63282af5 completed April 29, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69f118afabd88190bd88f49597d120e8 completed April 28, 2026, 8:29 p.m.
Created at: April 17, 2026, 6:11 p.m.