Triple
T16447316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hexi Corridor |
E399464
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Wuwei |
E1130941
|
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: Wuwei | Statement: [Hexi Corridor, contains, Wuwei]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wuwei Context triple: [Hexi Corridor, contains, Wuwei]
-
A.
Luzhi
Luzhi is an ancient canal town near Suzhou in China, renowned for its well-preserved waterways, stone bridges, and traditional Jiangnan architecture.
-
B.
Jianye
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
-
C.
Wuwei City
chosen
Wuwei City is a prefecture-level city in central Gansu Province, China, historically known as a key stop on the ancient Silk Road.
-
D.
Yuanxing
Yuanxing was the era name used by Eastern Wu emperor Sun Hao during part of his tumultuous late Three Kingdoms–period reign in China.
-
E.
Wuyuan
Wuyuan is a historic county in northeastern Jiangxi, China, famed for its well-preserved Huizhou-style architecture and picturesque rural landscapes.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cddfc3c8190919b49f74b7e8e1a |
completed | April 18, 2026, 7:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a005815efc48190868305f428cb9085 |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:10 a.m.