Triple
T862612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novaya Gazeta |
E18629
|
entity |
| Predicate | riskLevelForStaff |
P3842
|
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: [Novaya Gazeta, riskLevelForStaff, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskLevelForStaff Context triple: [Novaya Gazeta, riskLevelForStaff, very high]
-
A.
riskLevel
chosen
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
B.
riskProfile
Indicates the level and characteristics of potential risk associated with an entity, action, or situation.
-
C.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
D.
riskGroup
Indicates that an entity belongs to a category of individuals or items that share an elevated level of risk relative to others.
-
E.
riskManagedBy
Indicates that the potential or identified risk is controlled, mitigated, or overseen through the actions, policies, or responsibilities of a specified managing entity.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac67d4d481909487d3edb3e46936 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.