Triple
T8257977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YN |
E193117
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Qujing |
E211404
|
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: Qujing | Statement: [YN, hasMajorCity, Qujing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Qujing Context triple: [YN, hasMajorCity, Qujing]
-
A.
Qujing
chosen
Qujing is a major prefecture-level city in eastern Yunnan Province, China, known as an important regional transportation and industrial hub.
-
B.
Dongjing
Dongjing is the historical name for Kaifeng when it served as the capital of the Northern Song dynasty in China.
-
C.
Licheng
Licheng is the courtesy name of the Daoguang Emperor, a Qing dynasty ruler of China in the early 19th century.
-
D.
Jianye
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
-
E.
Pingcheng
Pingcheng was an important ancient Chinese city that served as the early capital of the Northern Wei dynasty, located near present-day Datong in Shanxi Province.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78fce9308190ac36512e80b06b52 |
completed | March 31, 2026, 7:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf9fdde41081908de793672a889a67 |
completed | April 3, 2026, 11:09 a.m. |
Created at: March 30, 2026, 5:49 p.m.