Triple

T30189543
Position Surface form Disambiguated ID Type / Status
Subject RCP3-PD E767433 entity
Predicate hasMitigationLevel P180536 FINISHED
Object very high 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: very high | Statement: [RCP3-PD, hasMitigationLevel, very high]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMitigationLevel
Context triple: [RCP3-PD, hasMitigationLevel, very high]
  • A. requiresMitigation
    Indicates that something poses a risk or issue that must be addressed through specific mitigation actions or measures.
  • B. builtAsMitigationFor
    Indicates that one entity was constructed specifically to reduce, prevent, or counteract a particular risk, problem, or adverse impact associated with another entity.
  • C. mitigationStrategy
    Indicates a relationship where one entity serves as a method or approach used to reduce, control, or lessen the negative impact, risk, or severity associated with another entity or situation.
  • D. hasHazardLevel
    Indicates that an entity is associated with a specified degree or category of risk or danger.
  • E. hasConditionalityLevel
    Indicates that one entity is associated with a specific degree or level of conditional requirements, constraints, or dependencies relative to another entity or context.
  • F. None of above. chosen

Provenance (4 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_69f2247cc3d88190811dec3face94bf5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7431c0eec81909ead443e07d75e18 completed May 3, 2026, 12:44 p.m.
PD Predicate disambiguation batch_69f74143cf708190a12d487884298437 completed May 3, 2026, 12:36 p.m.
PDg Predicate description generation batch_69f7431aac148190bb6aac59817c174a completed May 3, 2026, 12:44 p.m.
Created at: April 29, 2026, 7:28 p.m.