Triple
T9798827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona State Prison |
E237783
|
entity |
| Predicate | securityClassifications |
P51148
|
FINISHED |
| Object | multiple security levels |
—
|
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: multiple security levels | Statement: [Arizona State Prison, securityClassifications, multiple security levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityClassifications Context triple: [Arizona State Prison, securityClassifications, multiple security levels]
-
A.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
governmentClassification
Indicates that an entity is assigned a specific status or category according to a government’s official classification system.
-
C.
hasSecurityClass
chosen
Indicates that an entity is assigned to or associated with a particular security classification level.
-
D.
isoClassificationStatus
Indicates the current status or stage of an entity within an ISO-based classification or standardization process.
-
E.
protectionCategory
Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda627cc2c81909ccc2e26751f5e85 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.