Triple
T23030804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minimum Operating Residential Security Standards |
E573447
|
entity |
| Predicate | riskLevelBasis |
P26874
|
FINISHED |
| Object | security risk level of the duty station |
—
|
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: security risk level of the duty station | Statement: [Minimum Operating Residential Security Standards, riskLevelBasis, security risk level of the duty station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskLevelBasis Context triple: [Minimum Operating Residential Security Standards, riskLevelBasis, security risk level of the duty station]
-
A.
riskBasis
chosen
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
B.
riskLevel
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
C.
riskBased
Indicates that something is determined, prioritized, or managed according to the level or assessment of risk involved.
-
D.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
E.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18481072c81909ab2a2c87e034433 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.