Triple

T87044
Position Surface form Disambiguated ID Type / Status
Subject Kato Svanidze E1749 entity
Predicate hasRoleIn P161 FINISHED
Object early life of Joseph Stalin 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 life of Joseph Stalin | Statement: [Kato Svanidze, hasRoleIn, early life of Joseph Stalin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRoleIn
Context triple: [Kato Svanidze, hasRoleIn, early life of Joseph Stalin]
  • A. hasRole chosen
    Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
  • B. hasAccessTo
    Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
  • C. isGrantedFor
    Indicates that a permission, right, or benefit has been formally given to a specific entity for a particular purpose or use.
  • D. hasAuthorityStatus
    Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
  • E. hasScope
    Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
  • 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_69a24c8150408190910a693eb51c1f71 completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a2503d304c8190a0034ffa4a38a501 completed Feb. 28, 2026, 2:17 a.m.
PD Predicate disambiguation batch_69a24eb6da2c8190a33d144d219f7abe completed Feb. 28, 2026, 2:11 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.