Triple

T16138389
Position Surface form Disambiguated ID Type / Status
Subject Caizhou E391588 entity
Predicate predecessorCapital P3417 FINISHED
Object Bianjing E131801 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: Bianjing | Statement: [Caizhou, predecessorCapital, Bianjing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bianjing
Context triple: [Caizhou, predecessorCapital, Bianjing]
  • A. Kaifeng chosen
    Kaifeng is an ancient city in eastern Henan, China, historically significant as a former capital of several Chinese dynasties and a major cultural and economic center.
  • B. Zhongdu
    Zhongdu was the historical capital city of the Jurchen-led Jin dynasty in northern China, located in what is now part of modern Beijing.
  • C. Luoyang
    Luoyang is one of China’s oldest and most historically significant cities, renowned as an ancient imperial capital and cultural center along the Yellow River.
  • D. Yuan Dadu
    Yuan Dadu was the capital city of the Yuan dynasty in China, located on the site of present-day Beijing and serving as a major political and cultural center of the Mongol-ruled empire.
  • E. Bianzhou
    Bianzhou was an important administrative and strategic city during China’s Later Liang dynasty in the Five Dynasties period.
  • 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_69d87f1bb0988190b490d273dbf3fd03 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21a06e0988190b5cd62d422d058a2 completed April 17, 2026, 11:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a001f83f6ac8190b9f18fe701a9b3ce completed May 10, 2026, 6:02 a.m.
Created at: April 10, 2026, 5:01 a.m.