Triple

T21158915
Position Surface form Disambiguated ID Type / Status
Subject Life Savers, Inc. E521383 entity
Predicate notableFeatureOfProduct P46274 FINISHED
Object ring-shaped candy design 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: ring-shaped candy design | Statement: [Life Savers, Inc., notableFeatureOfProduct, ring-shaped candy design]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableFeatureOfProduct
Context triple: [Life Savers, Inc., notableFeatureOfProduct, ring-shaped candy design]
  • A. notableFeatureOn
    Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
  • B. notableTechnicalFeature
    Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
  • C. 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.
  • D. notableGameFeature
    Indicates that a particular game feature is especially significant, distinctive, or noteworthy in the context of the game.
  • E. notableStyleFeature chosen
    Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
  • 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_69e0b50d1ea481909c07e63c3ead9316 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7252e9ef481908f4904c535f3da8b completed April 21, 2026, 7:20 a.m.
PD Predicate disambiguation batch_69e5f5f8a5bc819081918c7fa8e4496d completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 2:59 p.m.