Triple

T589131
Position Surface form Disambiguated ID Type / Status
Subject Battle of Beiping–Tianjin E17227 entity
Predicate location P40 FINISHED
Object Beiping 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: Beiping | Statement: [Battle of Beiping–Tianjin, location, Beiping]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beiping
Context triple: [Battle of Beiping–Tianjin, location, Beiping]
  • 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. Chengde
    Chengde is a historic city in northeastern China best known for its Qing dynasty Mountain Resort, a vast imperial summer retreat and UNESCO World Heritage Site.
  • C. 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.
  • D. Tianjin
    Tianjin is a major port city and industrial hub in northern China, located near Beijing along the Bohai Sea.
  • E. Baoding
    Baoding is a historic prefecture-level city in central Hebei Province, China, known as a regional transportation hub and former military and administrative center.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49bb775fc819085b968f8615dca59 completed March 1, 2026, 8:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad0e5413448190bd9112e2b3d83826 completed March 8, 2026, 5:51 a.m.
Created at: March 1, 2026, 7:33 p.m.