Triple
T30636960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Jewish ghetto area |
E779866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wartime enclave |
C47723
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: wartime enclave Context triple: [Shanghai Jewish ghetto area, instanceOf, wartime enclave]
-
A.
wartime entity
A wartime entity is an organized group, institution, or structure that operates within or because of armed conflict, influencing or participating in military, political, economic, or social aspects of war.
-
B.
wartime settlement
A wartime settlement is an agreement or arrangement reached during or immediately after armed conflict that defines the terms for ending hostilities, addressing territorial or political disputes, and establishing conditions for postwar order.
-
C.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
D.
World War II ghetto
chosen
A World War II ghetto was a segregated, enclosed urban district where Nazi authorities forcibly confined Jews (and sometimes other targeted groups) under overcrowded, impoverished, and brutal conditions as part of their broader system of persecution and genocide.
-
E.
wartime command centre
A wartime command centre is a secure, centralized facility where military leaders gather, analyze real-time intelligence, coordinate operations, and issue strategic and tactical orders during armed conflict.
- F. None of above.
Provenance (1 batch)
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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:28 p.m.