Triple
T1104597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wushe Incident |
E25457
|
entity |
| Predicate | methodOfSuppression |
P859
|
FINISHED |
| Object | use of regular Japanese troops |
—
|
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: use of regular Japanese troops | Statement: [Wushe Incident, methodOfSuppression, use of regular Japanese troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfSuppression Context triple: [Wushe Incident, methodOfSuppression, use of regular Japanese troops]
-
A.
suppressedDuring
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
-
B.
methodOfDisappearance
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
-
C.
usedSupplyMethod
Indicates that an entity employed a particular method or process to supply or deliver something.
-
D.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
E.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.