Triple
T14917168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Legation in Peking |
E371409
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Beijing |
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: Beijing | Statement: [British Legation in Peking, location, Beijing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beijing Context triple: [British Legation in Peking, location, Beijing]
-
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.
Pekin
Pekin is a small hamlet in Niagara County, New York, known historically as a stop on the Underground Railroad.
-
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.
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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62038508190946499cd3552990e |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72a347808190a72dfd3a1b776982 |
completed | May 8, 2026, 11:32 p.m. |
Created at: April 10, 2026, 2:32 a.m.