Triple
T23583664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plötzensee Prison |
E582276
|
entity |
| Predicate | inUseAsExecutionSiteUntil |
P50547
|
FINISHED |
| Object | 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: 1945 | Statement: [Plötzensee Prison, inUseAsExecutionSiteUntil, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUseAsExecutionSiteUntil Context triple: [Plötzensee Prison, inUseAsExecutionSiteUntil, 1945]
-
A.
mainExecutionSiteDuring
Indicates that an entity primarily carries out its activities or operations at a particular site during a specified time period.
-
B.
keyExecutionSite
Indicates the location or context in which a key (e.g., cryptographic or access key) is actually used or executed.
-
C.
executedIn
chosen
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
-
D.
usedAsRelocationSiteDuring
Indicates that one entity served as a relocation site for another entity during a specified time or event.
-
E.
isExecutedFor
Indicates that an action, plan, or process is carried out on behalf of, or in service of, a particular entity or purpose.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02e19808190a41bce305f6cd5da |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:40 p.m.