Triple
T7942227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ian Brady |
E184416
|
entity |
| Predicate | heldAtHighSecurityHospital |
P22425
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ian Brady, heldAtHighSecurityHospital, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldAtHighSecurityHospital Context triple: [Ian Brady, heldAtHighSecurityHospital, yes]
-
A.
hospitalizedIn
chosen
Indicates that a person or patient is admitted for medical care and staying as an inpatient in a specified hospital or healthcare facility.
-
B.
containsHospital
Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
-
C.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
D.
heldInSolitaryConfinement
Indicates that an entity is subjected to isolation from others, typically as a form of confinement or punishment, where they are kept alone for extended periods.
-
E.
placeOfDetention
Indicates the location or facility where an entity is or was held in detention.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0c16b8819093c5d1719cd65ee3 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.