Triple
T32864585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadamar Memorial Site |
E840612
|
entity |
| Predicate | periodOfUseAsKillingCenter |
P4017
|
FINISHED |
| Object | 1941–1945 |
—
|
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: 1941–1945 | Statement: [Hadamar Memorial Site, periodOfUseAsKillingCenter, 1941–1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfUseAsKillingCenter Context triple: [Hadamar Memorial Site, periodOfUseAsKillingCenter, 1941–1945]
-
A.
operatedConcentrationCamp
Indicates that an entity was responsible for running, managing, or administering the operations of a concentration camp.
-
B.
exterminationCamp
Indicates a facility specifically established and operated for the systematic mass murder and annihilation of targeted groups of people.
-
C.
purposeDuringHolocaust
Indicates that something’s purpose, role, or intended function is specifically situated within the historical context of the Holocaust.
-
D.
periodOfMajorUse
chosen
Indicates the time span during which something was primarily or most intensively used.
-
E.
periodOfUseAsPrison
Indicates the time span during which something functioned or was used as a prison.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:17 a.m.