Triple

T6370146
Position Surface form Disambiguated ID Type / Status
Subject Convention of Peking E143324 entity
Predicate signedIn P441 FINISHED
Object Peking E2312 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: Peking | Statement: [Convention of Peking, signedIn, Peking]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Peking
Context triple: [Convention of Peking, signedIn, Peking]
  • A. Beijing chosen
    Beijing is the capital city of China, a major political, cultural, and economic center known for its rich history and rapid modern development.
  • B. Tiāntán
    Tiāntán is the Chinese pinyin name for the Temple of Heaven, a historic imperial religious complex in Beijing where Ming and Qing dynasty emperors performed annual ceremonies to pray for good harvests.
  • C. 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.
  • D. Shanghai
    Shanghai is a major global financial hub and China’s largest city, known for its modern skyline, historic waterfront, and role as a center of international business and trade.
  • E. Shanghai
    Shanghai is a major Ethereum network upgrade that introduced key changes such as enabling staked ETH withdrawals and improving the protocol’s efficiency and flexibility.
  • 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_69c008d8c61081908bcaf61510d881ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c068277f6c81908e6a55e006f0c229 completed March 22, 2026, 10:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c65fc0d90c8190abf85b591e90e292 completed March 27, 2026, 10:45 a.m.
Created at: March 22, 2026, 4:33 p.m.