Triple

T35365969
Position Surface form Disambiguated ID Type / Status
Subject Goldsmith’s E1021628 entity
Predicate hadBrandRole P121560 FINISHED
Object local anchor store in Memphis shopping districts 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: local anchor store in Memphis shopping districts | Statement: [Goldsmith’s, hadBrandRole, local anchor store in Memphis shopping districts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadBrandRole
Context triple: [Goldsmith’s, hadBrandRole, local anchor store in Memphis shopping districts]
  • A. hasBrandRole chosen
    Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
  • B. holdersPlayedRoleIn
    Indicates that the holders of something (e.g., a position, title, or asset) participated in or contributed to a particular role within an event, activity, or context.
  • C. hasBrandIdentityElement
    Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
  • D. hasBrandFounderRole
    Indicates that an entity holds or has held the role of founder for a particular brand.
  • E. hadStaffRole
    Indicates that an entity served in a specific staff role or position for another entity during some period.
  • 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_69f76df000488190ab7c97f565677055 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f79533b88c8190934ec4cb21770e24 completed May 3, 2026, 6:34 p.m.
PD Predicate disambiguation batch_69f79104f5b48190a496cdffde8472da completed May 3, 2026, 6:16 p.m.
Created at: May 3, 2026, 4:03 p.m.