Triple

T16369682
Position Surface form Disambiguated ID Type / Status
Subject The Orchid House E397530 entity
Predicate hasSalesDescriptor P115460 FINISHED
Object international bestseller 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: international bestseller | Statement: [The Orchid House, hasSalesDescriptor, international bestseller]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSalesDescriptor
Context triple: [The Orchid House, hasSalesDescriptor, international bestseller]
  • A. hasMarketingDescription chosen
    Indicates that an entity is associated with a textual marketing-oriented description used to promote or present it.
  • B. hasRetailCharacteristic
    Indicates that an entity possesses a specific attribute, feature, or quality relevant to retail contexts (such as pricing, packaging, or point-of-sale properties).
  • C. isSoldIn
    Indicates that a product or item is available for purchase within a specified location, market, or sales channel.
  • D. isTypicallySoldAs
    Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
  • E. hasTradeCharacteristic
    Indicates that an entity possesses a specific trade-related attribute, quality, or feature.
  • 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_69d87f2778dc8190aa95c7572db127e6 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2ff4021e88190ad093bab74cf82a4 completed April 18, 2026, 3:49 a.m.
PD Predicate disambiguation batch_69e226f37ecc819082af58b29b4e39d1 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:08 a.m.