Triple

T32562625
Position Surface form Disambiguated ID Type / Status
Subject Tatishchev E832267 entity
Predicate notableMemberContribution P477 FINISHED
Object early systematic history of Russia 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: early systematic history of Russia | Statement: [Tatishchev, notableMemberContribution, early systematic history of Russia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableMemberContribution
Context triple: [Tatishchev, notableMemberContribution, early systematic history of Russia]
  • A. notableContribution chosen
    Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
  • B. notableContributionField
    Indicates the field or domain in which an entity has made a significant or noteworthy contribution.
  • C. notableFor
    Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
  • D. notableMemberBecame
    Indicates that an individual who is a notable member of one group, organization, or category transitioned into or assumed a role, status, or membership in another.
  • E. notableImpactOn
    Indicates that one entity has had a significant, recognizable, or influential effect on another 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_69f34926b9848190ace47d2dd0a0de7c completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379edf2d88190b492fca86ed23cac completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:03 a.m.