Triple

T33914610
Position Surface form Disambiguated ID Type / Status
Subject Too Busy Thinking About My Baby E869416 entity
Predicate backingLabelImprint P49200 FINISHED
Object Motown Records NE NERFINISHED

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: Motown Records | Statement: [Too Busy Thinking About My Baby, backingLabelImprint, Motown Records]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: backingLabelImprint
Context triple: [Too Busy Thinking About My Baby, backingLabelImprint, Motown Records]
  • A. associatedLabelOrImprint chosen
    Indicates a relationship where one entity serves as the label or imprint formally linked to, or published in association with, another entity.
  • B. imprintedOn
    Indicates that one entity has formed a strong, often early-life, attachment or bond to another entity, typically treating it as a primary reference or caregiver.
  • C. recordLabelImprint
    Indicates that one record label functions as an imprint (a subsidiary or brand) of another record label.
  • D. hadImprint
    Indicates that one entity bears or once bore a physical or symbolic mark, stamp, or impression produced by another entity.
  • E. hasSubImprint
    Indicates that one imprint functions as a subordinate or subsidiary imprint under another imprint.
  • 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_69f3499869bc8190b6c33a81686af226 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:48 a.m.