Triple

T7460806
Position Surface form Disambiguated ID Type / Status
Subject District of Columbia Office of Risk Management E176242 entity
Predicate typeOfRiskManaged P15871 FINISHED
Object operational 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: operational risk | Statement: [District of Columbia Office of Risk Management, typeOfRiskManaged, operational risk]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfRiskManaged
Context triple: [District of Columbia Office of Risk Management, typeOfRiskManaged, operational risk]
  • A. riskTypesManaged
    Indicates that one entity is responsible for handling, controlling, or overseeing specific categories of risk associated with another entity or context.
  • B. riskManagedBy
    Indicates that the potential or identified risk is controlled, mitigated, or overseen through the actions, policies, or responsibilities of a specified managing entity.
  • C. riskType chosen
    Indicates the category or nature of risk associated with an entity, event, or relationship.
  • D. riskManagement
    Indicates the implementation of strategies and actions to identify, assess, and mitigate potential risks associated with an entity or activity.
  • E. riskBasis
    Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
  • 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_69c69f21632481908bf83f6c6da897e3 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f3d525708190b7838e07ac2fbe1f completed March 27, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69c6f03bad9c8190bdd5abb86d37df47 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:38 p.m.