Triple

T22649286
Position Surface form Disambiguated ID Type / Status
Subject Yum! Brands, Inc. E559051 entity
Predicate stockSymbol P1447 FINISHED
Object YUM NE NERFINISHED

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: YUM | Statement: [Yum! Brands, Inc., stockSymbol, YUM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: YUM
Context triple: [Yum! Brands, Inc., stockSymbol, YUM]
  • A. YUM
    YUM is a command-line package management utility for RPM-based Linux distributions that automatically handles software installation, updates, and dependency resolution.
  • B. YUM chosen
    YUM is the stock ticker symbol for Yum! Brands, the multinational fast-food corporation that owns KFC, Taco Bell, and Pizza Hut.
  • C. YUM
    YUM is the IATA airport code for Marine Corps Air Station Yuma, a joint-use military and civilian airfield in Yuma, Arizona.
  • D. YAM
    YAM is the IATA airport code for Sault Ste. Marie Airport in Ontario, Canada.
  • E. Subby
    Subby is a character from the Kraken universe, typically depicted as a quirky, sea-themed figure associated with the brand’s nautical mythos.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1703a84b081909a683f8c850dcbf9 completed April 29, 2026, 2:43 a.m.
Created at: April 17, 2026, 3:05 p.m.