Triple
T16071279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stolpersteine |
E389866
|
entity |
| Predicate | placementCriterion |
P98362
|
FINISHED |
| Object | last freely chosen place of residence |
—
|
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: last freely chosen place of residence | Statement: [Stolpersteine, placementCriterion, last freely chosen place of residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placementCriterion Context triple: [Stolpersteine, placementCriterion, last freely chosen place of residence]
-
A.
compositionCriterion
Indicates the rule or standard by which components are selected, combined, or arranged to form a whole.
-
B.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
C.
zoneAssignmentCriterion
Indicates the rule or condition used to determine how entities are assigned to a particular zone or area.
-
D.
listingCriterion
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
-
E.
placementType
chosen
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.