Triple
T28076009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhongwu |
E709543
|
entity |
| Predicate | hasPosthumousNature |
P4225
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zhongwu, hasPosthumousNature, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPosthumousNature Context triple: [Zhongwu, hasPosthumousNature, yes]
-
A.
isPosthumous
chosen
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
B.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
C.
isPosthumousCollaboration
Indicates that a work results from a collaboration where at least one contributor was already deceased when the collaboration occurred or the work was completed.
-
D.
posthumousProductionInvolvement
Indicates involvement in the production, release, or completion of a work that occurred after the primary contributor’s death.
-
E.
posthumousPresence
Indicates the continued influence, impact, or perceived presence of an entity after its death or cessation of existence.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 27, 2026, 8:49 p.m.