Triple
T9990305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | former Stasi remand prison Berlin-Hohenschönhausen |
E196868
|
entity |
| Predicate | accessStatusDuringGDR |
P9584
|
FINISHED |
| Object | secret location |
—
|
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: secret location | Statement: [former Stasi remand prison Berlin-Hohenschönhausen, accessStatusDuringGDR, secret location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessStatusDuringGDR Context triple: [former Stasi remand prison Berlin-Hohenschönhausen, accessStatusDuringGDR, secret location]
-
A.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
B.
accessDeterminedBy
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
-
C.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
D.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
E.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc7a0cb6481908d7bd1b43f93bd18 |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.