Triple
T16822983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhu Shizhen |
E408941
|
entity |
| Predicate | posthumousRole |
P69095
|
FINISHED |
| Object | progenitor of the imperial Zhu family |
—
|
LITERAL 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: progenitor of the imperial Zhu family | Statement: [Zhu Shizhen, posthumousRole, progenitor of the imperial Zhu family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousRole Context triple: [Zhu Shizhen, posthumousRole, progenitor of the imperial Zhu family]
-
A.
posthumousTitleOf
Indicates that one entity is the honorary or formal title granted to another entity after that entity’s death.
-
B.
posthumousAssociation
Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
-
C.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
D.
posthumousHolder
chosen
Indicates that an entity is recognized as holding a title, role, or status only after their death.
-
E.
posthumousAction
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
- F. None of above.
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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e838e881908b650194c9b94886 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.