Triple
T19285221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punggol Beach |
E482292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II massacre site |
C11664
|
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: World War II massacre site Context triple: [Punggol Beach, instanceOf, World War II massacre site]
-
A.
Holocaust site
A Holocaust site is a location directly associated with the persecution, deportation, forced labor, or mass murder of Jews and other targeted groups by Nazi Germany and its collaborators during the Holocaust.
-
B.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
C.
World War II incarceration camp
A World War II incarceration camp is a government-run facility where civilians or prisoners of war were forcibly confined, often without due process, under harsh and restrictive conditions during the Second World War.
-
D.
war crime site
chosen
A war crime site is a specific location where serious violations of the laws and customs of war have been committed, investigated, or memorialized, often serving as evidence in legal proceedings and as a place of historical record.
-
E.
Holocaust- and World War II–related memorial
A Holocaust- and World War II–related memorial is a physical or symbolic structure, space, or installation created to commemorate the victims, events, and consequences of the Holocaust and World War II, fostering remembrance, education, and reflection.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:30 p.m.