Triple
T8618301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhou state |
E204097
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Haojing |
E233751
|
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: Haojing | Statement: [Zhou state, capital, Haojing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haojing Context triple: [Zhou state, capital, Haojing]
-
A.
Haojing
chosen
Haojing was the primary western capital city of the early Zhou dynasty in ancient China, located near present-day Xi’an.
-
B.
Shangjing
Shangjing was the principal early capital city of China’s Jurchen-led Jin dynasty, serving as a key political and administrative center in northeastern China.
-
C.
Shangjing
Shangjing was the principal imperial capital city of the Khitan-led Liao dynasty in what is now northeastern China.
-
D.
Xinjing
Xinjing was the capital city of the Japanese puppet state of Manchukuo in northeastern China during the 1930s and early 1940s.
-
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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4712e74c81908b607a0ab2f9a361 |
completed | March 31, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfb9f4e2d881908fb539e842c20e8d |
completed | April 3, 2026, 1 p.m. |
Created at: March 30, 2026, 6:26 p.m.