Triple

T31591659
Position Surface form Disambiguated ID Type / Status
Subject BBY E806112 entity
Predicate hasTickerSuffix P130930 FINISHED
Object 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:  | Statement: [BBY, hasTickerSuffix, ]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTickerSuffix
Context triple: [BBY, hasTickerSuffix, ]
  • A. hasNameSuffix
    Indicates that an entity’s name includes a specific suffix or ending component.
  • B. hasLetterSuffix chosen
    Indicates that an entity’s identifier, name, or code ends with a specific letter or sequence of letters.
  • C. hasTierName
    Indicates that an entity is associated with a specific tier by its name.
  • D. hasSuffixedRoute
    Indicates that a route is a variant or extension of another base route, distinguished by an added suffix in its identifier.
  • E. hasSuccessorSponsoredName
    Indicates that an entity has a successor whose name reflects sponsorship, typically replacing or following the original name due to a sponsorship agreement.
  • 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_69f348d4891c8190b02bae3c8ecb68b7 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fce28d6c3081908bf76f5db63ecf68 completed May 7, 2026, 7:05 p.m.
PD Predicate disambiguation batch_69fce12d2f08819082134b5eb3db6a24 completed May 7, 2026, 6:59 p.m.
Created at: April 30, 2026, 10:28 p.m.