Triple

T38541993
Position Surface form Disambiguated ID Type / Status
Subject Summer Shandy E924856 entity
Predicate introducedAsSeasonal P163379 FINISHED
Object yes 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: yes | Statement: [Summer Shandy, introducedAsSeasonal, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedAsSeasonal
Context triple: [Summer Shandy, introducedAsSeasonal, yes]
  • A. isSeasonalRelease chosen
    Indicates that something is released only during a specific season or limited time period tied to the calendar.
  • B. hasSeasonalHighlight
    Indicates that something features a notable or emphasized aspect during a particular season or time of year.
  • C. usedInSeason
    Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
  • D. usedSeasonallyBy
    Indicates that something is utilized or employed by an entity only during specific seasons or times of the year.
  • E. hasSeasonalNature
    Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
  • 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_69f76eadeac081909cdfdd0474cb6765 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ff21cbd9108190a52c0ba42004c669 completed May 9, 2026, noon
PD Predicate disambiguation batch_69ff1faea91881908c626c70bca5100a completed May 9, 2026, 11:51 a.m.
Created at: May 3, 2026, 4:32 p.m.