Triple
T16543188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 四人帮 |
E401871
|
entity |
| Predicate | 历史评价 |
P675
|
FINISHED |
| Object | 被认为加剧文化大革命的混乱 |
—
|
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: 被认为加剧文化大革命的混乱 | Statement: [四人帮, 历史评价, 被认为加剧文化大革命的混乱]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 历史评价 Context triple: [四人帮, 历史评价, 被认为加剧文化大革命的混乱]
-
A.
historicalAssessment
chosen
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
B.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
C.
characterizationByHistorians
Indicates how historians have described, interpreted, or evaluated a person, event, or phenomenon in their scholarly work.
-
D.
historiographicalStatus
Indicates the recognized standing or classification of something within historical writing or scholarship, such as how it is interpreted, debated, or valued by historians.
-
E.
historicalTheory
Indicates a relationship where an entity is recognized as a theory or interpretive framework concerning past events or historical processes.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455fab34819086c77ff45b85f5db |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.