Triple
T24120273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuengamme concentration camp |
E597633
|
entity |
| Predicate | convertedToMainCamp |
P131306
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [Neuengamme concentration camp, convertedToMainCamp, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToMainCamp Context triple: [Neuengamme concentration camp, convertedToMainCamp, 1940]
-
A.
hadCamp
Indicates that an entity conducted, hosted, or participated in a camp event or camping activity.
-
B.
convertedToSegregationCenter
chosen
Indicates that an entity has been transformed or repurposed into a segregation center, where individuals or items are separated or isolated based on specified criteria.
-
C.
endedInMainColony
Indicates that an event, process, or entity concluded within the primary or central colony rather than elsewhere.
-
D.
relocatedAndBecame
Indicates that an entity moved from one place to another and, as a result of this move, assumed a new role, status, or identity.
-
E.
convertedToSchoolIn
Indicates that something has been transformed or repurposed into a school within a specified location or context.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee2defc81909df55900769fef5b |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.