Triple
T17445554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Wei |
E424772
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Yecheng |
—
|
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: Yecheng | Statement: [Eastern Wei, capital, Yecheng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yecheng Context triple: [Eastern Wei, capital, Yecheng]
-
A.
Yecheng
chosen
Yecheng was an important ancient Chinese city that served as a major political and cultural center in northern China during several dynasties.
-
B.
Yutian
Yutian is the ancient name of the oasis kingdom and region historically known as Hotan on the southern Silk Road in what is now Xinjiang, China.
-
C.
Zhangye
Zhangye is a historic city in northwestern China, known for its location on the ancient Silk Road and its colorful Danxia landform landscapes.
-
D.
Daiyuan
Daiyuan is a given name most notably associated with Teng Daiyuan, a prominent Chinese Communist revolutionary and political leader.
-
E.
Quchan
Quchan is a historic city in northeastern Iran known for its strategic location along trade routes and its role as a regional center in the Khorasan area.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffafec48190b25980318cea353f |
completed | April 19, 2026, 3:46 a.m. |
Created at: April 10, 2026, 5:47 a.m.