Triple
T25633720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiʻi State Hospital |
E642636
|
entity |
| Predicate | patientSecurityLevel |
P60827
|
FINISHED |
| Object | high-risk |
—
|
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: high-risk | Statement: [Hawaiʻi State Hospital, patientSecurityLevel, high-risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patientSecurityLevel Context triple: [Hawaiʻi State Hospital, patientSecurityLevel, high-risk]
-
A.
securityLevelDetail
Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
-
B.
protectionLevel
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
C.
typicalSecurityLevel
chosen
Indicates the usual or standard security level that is generally applied or expected in a given context or system.
-
D.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
E.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6009b48190a0e1f42da97f8533 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 5:19 p.m.