Triple
T13680484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Detention Centre, Scheveningen |
E327986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-security facility |
C3471
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: high-security facility Context triple: [ICC Detention Centre, Scheveningen, instanceOf, high-security facility]
-
A.
secure facility
A secure facility is a controlled-access location designed with physical, technical, and procedural safeguards to protect people, assets, and sensitive information from unauthorized access or harm.
-
B.
secure storage facility
A secure storage facility is a highly protected, access-controlled environment designed to safely store valuable, sensitive, or hazardous items against theft, damage, and unauthorized access.
-
C.
high-security psychiatric hospital
A high-security psychiatric hospital is a specialized medical facility designed to provide intensive mental health treatment and constant supervision for individuals who pose a significant risk of harm to themselves or others, within a highly controlled and secure environment.
-
D.
intelligence agency facility
An intelligence agency facility is a secure, specialized complex where classified information is collected, analyzed, stored, and operations are coordinated to support national security and intelligence objectives.
-
E.
correctional facility
chosen
A correctional facility is a secure institution where individuals convicted of crimes are confined, supervised, and provided with programs aimed at punishment, rehabilitation, and public safety.
- F. None of above.
Provenance (1 batch)
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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:53 p.m.