Triple
T2938485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Northeastern Army |
E79326
|
entity |
| Predicate | dispositionAfterLossOfManchuria |
P44065
|
FINISHED |
| Object | redeployed to North China |
—
|
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: redeployed to North China | Statement: [Chinese Northeastern Army, dispositionAfterLossOfManchuria, redeployed to North China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dispositionAfterLossOfManchuria Context triple: [Chinese Northeastern Army, dispositionAfterLossOfManchuria, redeployed to North China]
-
A.
roleInManchuria
Indicates that an entity holds or held a specific role, position, or function in the context of Manchuria.
-
B.
survivedSecondSinoJapaneseWar
Indicates that the subject continued to live through and beyond the duration of the Second Sino-Japanese War.
-
C.
MukdenIncidentYear
Indicates the specific year in which the Mukden Incident occurred.
-
D.
objectiveOfJapaneseForces
Indicates that a specified target, goal, or aim is the military objective pursued by Japanese forces.
-
E.
countrySurrendering
Indicates that one country formally yields to another country’s authority or control, typically ending a conflict or war.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad986c1c0c8190a6a9f17082438cfd |
completed | March 8, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.