Triple
T33017889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 杜聿明 |
E844824
|
entity |
| Predicate | 政治轉變 |
P47099
|
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.
politicalShift
chosen
Indicates a change in an entity’s political position, alignment, or governing structure over time.
-
B.
politicalChangeAssociatedWith
Indicates that one political change is connected or correlated with another event, condition, or transformation.
-
C.
mainPoliticalDevelopment
Indicates the primary or most significant political change, event, or evolution affecting an entity within a given period or context.
-
D.
causeOfChangeOfGovernment
Indicates a relationship where one entity is responsible for bringing about a change in the governing authority or political leadership of another entity.
-
E.
typeOfRegimeChange
Indicates a change in the form, structure, or governing system of a political regime, such as transitions between different types of rule or authority.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.