Triple
T13666172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jin (state) |
E327125
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Jiang (絳) |
E717345
|
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: Jiang (絳) | Statement: [Jin (state), capital, Jiang (絳)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jiang (絳) Context triple: [Jin (state), capital, Jiang (絳)]
-
A.
Jiang (絳)
chosen
Jiang (絳) was an ancient Chinese city that served as an early political and administrative center of the State of Jin during the Zhou dynasty.
-
B.
Jiang
Jiang is the modern standard pinyin romanization of a common Chinese surname historically spelled as "Chiang" in older romanization systems.
-
C.
Jianzhong
Jianzhong was a brief imperial era name used during the reign of Emperor Dezong in the Tang dynasty, marking a specific period in his rule.
-
D.
Yujian
Yujian was the personal name of the Longwu Emperor, a short-lived Ming dynasty claimant who resisted the Qing conquest in southern China.
-
E.
Jianxing
Jianxing was a historical Chinese era name used during the reign of Eastern Wu ruler Sun Quan in the Three Kingdoms period.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc623fcc88190bbad97541c040b7a |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78b0cfe0c8190b0fe50931e9788cf |
completed | May 3, 2026, 5:51 p.m. |
Created at: April 9, 2026, 9:52 p.m.