Triple
T35179693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amersfoort camp |
E1015812
|
entity |
| Predicate | usedForDeportationTo |
P193020
|
FINISHED |
| Object | Auschwitz concentration camp |
—
|
NE NERFINISHED |
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: Auschwitz concentration camp | Statement: [Amersfoort camp, usedForDeportationTo, Auschwitz concentration camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForDeportationTo Context triple: [Amersfoort camp, usedForDeportationTo, Auschwitz concentration camp]
-
A.
deportedTo
Indicates that an authority forcibly removed a person from one place or country and sent them to another specified destination.
-
B.
deportedUnder
Indicates that an entity was deported in accordance with, or by authority of, a specific law, policy, program, or legal provision.
-
C.
deportationMethod
Indicates the method or means by which a person or group is deported from a place.
-
D.
deportedBy
Indicates that an entity was expelled or removed from a country or territory by a specific authority, agent, or organization.
-
E.
deportedFrom
Indicates that an authority has expelled an entity from a particular place or country, forcing their departure from that location.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: May 3, 2026, 4:02 p.m.