Triple

T21681203
Position Surface form Disambiguated ID Type / Status
Subject Pavel Ivanovich Chichikov E535110 entity
Predicate usesCoverStory P145425 FINISHED
Object claims to manage estates and resettle serfs 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: claims to manage estates and resettle serfs | Statement: [Pavel Ivanovich Chichikov, usesCoverStory, claims to manage estates and resettle serfs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCoverStory
Context triple: [Pavel Ivanovich Chichikov, usesCoverStory, claims to manage estates and resettle serfs]
  • A. usedCover
    Indicates that one entity employed another entity as a protective or concealing cover in a given context.
  • B. locationCoverStory
    Indicates that a particular location is used as a cover or front to conceal the true nature, purpose, or activities associated with something or someone.
  • C. containsCoverOf
    Indicates that one entity includes within it a cover or covering representation of another entity.
  • D. isCoveredIn
    Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
  • E. isCoverOf
    Indicates that one entity functions as a protective or enclosing layer placed over another entity.
  • 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_69e0c469b6ec8190aee4cadd1527db91 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef96c69990819088a1134ecea09099 completed April 27, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69e6968abfdc81909cf9e0bd72db9eca completed April 20, 2026, 9:11 p.m.
PDg Predicate description generation batch_69e69cb4bcbc8190a4fc2d508df107be completed April 20, 2026, 9:37 p.m.
Created at: April 16, 2026, 6:43 p.m.