Triple
T35909835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig-Engelsdorf subcamp |
E1038574
|
entity |
| Predicate | prisonerSource |
P45939
|
FINISHED |
| Object | Buchenwald 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: Buchenwald concentration camp | Statement: [Leipzig-Engelsdorf subcamp, prisonerSource, Buchenwald concentration camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prisonerSource Context triple: [Leipzig-Engelsdorf subcamp, prisonerSource, Buchenwald concentration camp]
-
A.
prisonerOrigin
chosen
Indicates that a prisoner comes from, or is originally associated with, a specified place or source.
-
B.
prisonerOf
Indicates that one entity is held in custody or confinement by another entity, typically under legal or authoritative control.
-
C.
prisonerSide
Indicates that one party in a conflict, case, or situation is aligned with or belongs to the side of the prisoner.
-
D.
prisonerType
Indicates the classification or category assigned to a prisoner within a correctional or detention system.
-
E.
hasNotablePrisonerSource
Indicates a relationship where a source provides information or evidence about a notable prisoner.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa71a66c81909dba6a2c3466284c |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.