Triple
T22324428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 第二次上海事変 |
E551866
|
entity |
| Predicate | 交戦勢力 |
P137647
|
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.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
-
B.
involvedForcesType
Indicates the type or category of forces that participate in or are associated with a given event, interaction, or situation.
-
C.
warAdversary
Indicates that two entities are opponents or enemies engaged in a state of war or armed conflict.
-
D.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
E.
majorBelligerent
chosen
Indicates that an entity is a primary or principal participant in a conflict, war, or large-scale hostile engagement.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15767425481909547bfe294fe06de |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.