Triple
T10359976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Zhou |
E244107
|
entity |
| Predicate | chineseName |
P4878
|
FINISHED |
| Object | 周公旦 |
E858643
|
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: 周公旦 | Statement: [Duke of Zhou, chineseName, 周公旦]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 周公旦 Context triple: [Duke of Zhou, chineseName, 周公旦]
-
A.
周公
chosen
周公是中国西周初期著名的政治家和思想家，被视为制礼作乐、奠定周朝制度与儒家礼治传统的关键人物之一。
-
B.
Tang Shu Yu (唐叔虞)
Tang Shu Yu (唐叔虞) was an early Zhou dynasty noble and feudal lord who established the foundations of the State of Jin in ancient China.
-
C.
成湯
成湯 was the founding king of the Shang dynasty in ancient China, renowned for overthrowing the Xia dynasty and establishing a new royal order.
-
D.
King Wen of Zhou
King Wen of Zhou was an early Zhou ruler revered as a sage-king whose leadership and reforms laid the groundwork for the Zhou dynasty’s overthrow of the Shang and the establishment of a new political order in ancient China.
-
E.
Di Xin of Shang
Di Xin of Shang was the last king of the Shang dynasty in ancient China, known for his tyrannical rule and defeat at the hands of the Zhou in the Battle of Muye.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9609c4481908b7d72ecf1adaa73 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7953205cc8190ad7f28a7436049bc |
completed | April 9, 2026, 12:01 p.m. |
Created at: April 6, 2026, 11:59 a.m.