Triple
T33017891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 杜聿明 |
E844824
|
entity |
| Predicate | 獲釋原因 |
P22992
|
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.
reasonForRelease
chosen
Indicates the cause, justification, or circumstance that led to an entity being released.
-
B.
freeRelease
Indicates that one entity releases another from an obligation, constraint, or state without requiring payment or compensation.
-
C.
releaseObtainedBy
Indicates that a particular release results from, or is produced through, a specified obtaining or acquisition process.
-
D.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
-
E.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
- 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.