Triple
T17853728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gao Wei |
E445875
|
entity |
| Predicate | posthumousAssessment |
P5766
|
FINISHED |
| Object | blamed for rapid collapse of Northern Qi |
—
|
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: blamed for rapid collapse of Northern Qi | Statement: [Gao Wei, posthumousAssessment, blamed for rapid collapse of Northern Qi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousAssessment Context triple: [Gao Wei, posthumousAssessment, blamed for rapid collapse of Northern Qi]
-
A.
posthumousDiagnosis
Indicates that a diagnosis was made for an individual only after their death.
-
B.
posthumousAction
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
-
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.
posthumousReputation
chosen
Indicates the reputation or standing attributed to a person after their death.
-
E.
posthumousSuccess
Indicates that an entity achieves recognition, fame, or significant success only after its creator or originator has died.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49001d8b881908c8d4efc3d7ff04f |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.