Triple
T4419943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jialing River |
E95071
|
entity |
| Predicate | cityOnRiver |
P165
|
FINISHED |
| Object | Guangyuan |
E438113
|
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: Guangyuan | Statement: [Jialing River, cityOnRiver, Guangyuan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guangyuan Context triple: [Jialing River, cityOnRiver, Guangyuan]
-
A.
Guangyuan
chosen
Guangyuan is a prefecture-level city in northern Sichuan, China, known as a regional transport hub with historical and cultural significance along the upper reaches of the Jialing River.
-
B.
Jianyang
Jianyang is a county-level city in northern Fujian Province, China, known for its historical role in tea production and its location along the Min River.
-
C.
Jinyang
Jinyang is the historical name of the city now known as Taiyuan, a major urban and industrial center in northern China’s Shanxi province.
-
D.
Yuncheng
Yuncheng is a major city in southern Shanxi Province, China, known for its historical sites and role as a regional transportation and economic hub.
-
E.
Jianye
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551fae7c8190abafda0d78f02d89 |
completed | March 13, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b650e656148190be51f790dc3d5f4d |
completed | March 15, 2026, 6:25 a.m. |
Created at: March 12, 2026, 11:29 p.m.