Triple
T9976463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Wu of Zhou |
E196342
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ji |
E819841
|
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: Ji | Statement: [King Wu of Zhou, familyName, Ji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ji Context triple: [King Wu of Zhou, familyName, Ji]
-
A.
Ji
Ji was an ancient Chinese city that served as the political and cultural center of the State of Yan during the Zhou dynasty period.
-
B.
Ji
chosen
Ji is the ancestral clan name of the royal house of the Zhou dynasty in ancient China.
-
C.
Jie
Jie is the given name of Ke Jie, a prominent Chinese professional Go player and former world champion.
-
D.
Jish
Jish is a village in northern Israel, historically significant for its mixed Maronite Christian and Muslim population and its location near the Lebanese border.
-
E.
Ji Fa
Ji Fa, better known as King Wu of Zhou, was the founding monarch of China’s Zhou dynasty who overthrew the Shang dynasty and established a new royal order.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84d0d3c8190b268582bb79c8973 |
completed | April 2, 2026, 12:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d257d3fc308190b82b3731139d15cb |
completed | April 5, 2026, 12:38 p.m. |
Created at: March 30, 2026, 8:48 p.m.