Triple
T22540700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bianliang |
E557280
|
entity |
| Predicate | ChineseName |
P744
|
FINISHED |
| Object | 汴梁 |
—
|
NE NERFINISHED |
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: 汴梁 | Statement: [Bianliang, ChineseName, 汴梁]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 汴梁 Context triple: [Bianliang, ChineseName, 汴梁]
-
A.
中都
中都是中国历史上多座王朝曾经设立的都城名称之一，常用于指代金朝的首都（今北京一带）。
-
B.
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.
-
C.
彭城
彭城 is the historical Chinese name for the ancient city and region centered around present-day Xuzhou in Jiangsu Province, known as a significant political and military site throughout Chinese history.
-
D.
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.
-
E.
名城
名城 is the Japanese name for Meijō, commonly associated with Meijo University and the surrounding Meijō area in Nagoya, Japan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f3251808190a72b849157854d8d |
completed | April 29, 2026, 1:30 a.m. |
Created at: April 16, 2026, 8:51 p.m.