Triple

T17285357
Position Surface form Disambiguated ID Type / Status
Subject Beijing 2008 Olympic Mascot Design Team E419639 entity
Predicate product P490 FINISHED
Object Jingjing E86199 NE 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: Jingjing | Statement: [Beijing 2008 Olympic Mascot Design Team, product, Jingjing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jingjing
Context triple: [Beijing 2008 Olympic Mascot Design Team, product, Jingjing]
  • A. Jingjing chosen
    Jingjing is one of the five Fuwa mascots of the 2008 Beijing Summer Olympics, represented as a giant panda symbolizing happiness and prosperity.
  • B. Ziying
    Ziying was the last ruler of the Qin dynasty in ancient China, whose brief reign ended with the dynasty’s collapse and the rise of the Han.
  • C. Yingying
    Yingying is one of the five Fuwa mascots of the 2008 Beijing Summer Olympics, represented as a Tibetan antelope symbolizing health and athleticism.
  • D. Beibei
    Beibei is one of the five Fuwa mascots of the 2008 Beijing Summer Olympics, symbolizing prosperity and representing the element of water.
  • E. Jingyu
    Jingyu is a Chinese given name that can be used for people of any gender and carries various meanings depending on the characters used to write it.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d886da626481908a14ce7830329a35 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e4332cabdc8190bbc711ab806d53bf completed April 19, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a017955448481909c2464a14c2a9799 completed May 11, 2026, 6:38 a.m.
Created at: April 10, 2026, 5:40 a.m.