Triple
T10896575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peng Zhen |
E257325
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Zhen |
E712908
|
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: Zhen | Statement: [Peng Zhen, givenName, Zhen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zhen Context triple: [Peng Zhen, givenName, Zhen]
-
A.
Zhen
chosen
Zhen is a clever and agile fox thief who becomes Po’s new student and ally in the animated film "Kung Fu Panda 4."
-
B.
Shizhen
Shizhen is the given name of Li Shizhen, the renowned Ming dynasty physician and naturalist best known for compiling the monumental Chinese medical text "Compendium of Materia Medica."
-
C.
Zhenyuan
Zhenyuan was a regnal era of the Tang dynasty marked by Emperor Dezong’s efforts to stabilize imperial authority and restore central control after periods of rebellion and fragmentation.
-
D.
Zhenyuan
Zhenyuan was a late 19th-century Chinese ironclad battleship of the Beiyang Fleet that played a prominent role in the First Sino-Japanese War.
-
E.
Yinzhi
Yinzhi was a Qing dynasty imperial prince, known as one of the sons of the Kangxi Emperor of China.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d02e4c88190b8286078e90bf913 |
completed | April 9, 2026, 8:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e15519e620819090e492861de6a567 |
completed | April 16, 2026, 9:31 p.m. |
Created at: April 8, 2026, 9:21 p.m.