Triple
T5571483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 本間雅晴 |
E146211
|
entity |
| Predicate | 訴追理由 |
P64510
|
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.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
B.
lostClaimTo
Indicates that one entity previously held a right or ownership over something but no longer retains that claim, often due to transfer, forfeiture, or invalidation.
-
C.
remedySought
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
D.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
E.
litigates
Indicates that one party engages in legal action or conducts a lawsuit against or involving another party.
- F. None of above. chosen
Provenance (4 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020502a288190af37f9ebb88fccae |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:37 p.m.