Triple
T21100994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wei Lihuang |
E519902
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wei |
—
|
NE NERFINISHED |
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: Wei | Statement: [Wei Lihuang, familyName, Wei]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wei Context triple: [Wei Lihuang, familyName, Wei]
-
A.
Wei
chosen
Wei is a common Chinese surname with historical significance and numerous notable bearers across Chinese history and culture.
-
B.
Wei
Wei was an ancient Chinese state during the Warring States period, known for its early strength and later decline before being annexed by the rising Qin dynasty.
-
C.
Wen
Wen was the personal given name of Emperor Yizong, a ninth-century ruler of China’s Tang dynasty.
-
D.
Wen
Wen is the posthumous title of King Wen of Zhou, the virtuous and foundational ruler traditionally credited with laying the groundwork for the Zhou dynasty in ancient China.
-
E.
Wen
Wen is a Chinese surname borne by numerous individuals, including prominent political figures such as former premier Wen Jiabao.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5e16cc81908257ccf8c9a59117 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 2:53 p.m.