Triple
T6177385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xijing |
E137853
|
entity |
| Predicate | contrastedWith |
P278
|
FINISHED |
| Object | Dongjing |
E559814
|
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: Dongjing | Statement: [Xijing, contrastedWith, Dongjing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dongjing Context triple: [Xijing, contrastedWith, Dongjing]
-
A.
Dongjing
chosen
Dongjing is the historical name for Kaifeng when it served as the capital of the Northern Song dynasty in China.
-
B.
Qujing
Qujing is a major prefecture-level city in eastern Yunnan Province, China, known as an important regional transportation and industrial hub.
-
C.
Da Yuan
Da Yuan is the official Chinese name for the Yuan dynasty, the Mongol-ruled imperial dynasty that governed China from the late 13th to the mid-14th century.
-
D.
Jianye
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
-
E.
Xitang
Xitang is an ancient water town in eastern China renowned for its well-preserved canals, stone bridges, and traditional architecture.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc87bc48190834042d9c41d5b86 |
completed | March 22, 2026, 9:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c141bb426881908d5a1451b3619f03 |
completed | March 23, 2026, 1:35 p.m. |
Created at: March 22, 2026, 4:18 p.m.