Triple

T27399479
Position Surface form Disambiguated ID Type / Status
Subject Boris Morozov E691788 entity
Predicate consequenceOfPolicies P168947 FINISHED
Object outbreak of the 1648 Salt Riot in Moscow 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: outbreak of the 1648 Salt Riot in Moscow | Statement: [Boris Morozov, consequenceOfPolicies, outbreak of the 1648 Salt Riot in Moscow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOfPolicies
Context triple: [Boris Morozov, consequenceOfPolicies, outbreak of the 1648 Salt Riot in Moscow]
  • A. consequenceOfInfluence
    Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
  • B. consequenceOfReforms
    Indicates that something occurs as a result of, or is caused by, a set of reforms.
  • C. consequenceOfApplication
    Indicates that something occurs as a result or outcome of a particular application or use of something.
  • D. hasConsequence
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • E. exploresConsequencesOf
    Indicates that one entity investigates, analyzes, or examines the outcomes, implications, or effects resulting from another entity or event.
  • 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_69ef5204f7048190bf226a129858fc5b completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f67866e9248190b7ba218f9ca2ae8d completed May 2, 2026, 10:19 p.m.
PD Predicate disambiguation batch_69f675fd59608190b246383435e68fce completed May 2, 2026, 10:09 p.m.
PDg Predicate description generation batch_69f676c35f3481909b9ba18a5662d6ce completed May 2, 2026, 10:12 p.m.
Created at: April 27, 2026, 12:28 p.m.