Triple

T29472112
Position Surface form Disambiguated ID Type / Status
Subject Mikael Tariverdiev E747536 entity
Predicate hasWorkRecognizedAsClassicIn P152975 FINISHED
Object Soviet Union NE NERFINISHED

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: Soviet Union | Statement: [Mikael Tariverdiev, hasWorkRecognizedAsClassicIn, Soviet Union]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorkRecognizedAsClassicIn
Context triple: [Mikael Tariverdiev, hasWorkRecognizedAsClassicIn, Soviet Union]
  • A. hasWorkRecognizedBy
    Indicates that one entity’s work, creation, or contribution has been formally acknowledged, honored, or cited by another entity.
  • B. hasWorkRecognized chosen
    Indicates that an entity’s work, contribution, or achievement has been formally acknowledged or honored by another entity or authority.
  • C. hasWorkClassificationSystem
    Indicates that an entity is associated with a particular system used to classify or organize types of work.
  • D. hasTraditionalRecognition
    Indicates that an entity is acknowledged or honored according to established customs, practices, or longstanding cultural traditions.
  • E. hasSignificantWorkType
    Indicates that an entity is associated with a primary or notably important type or category of work.
  • 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_69f0bd42cf308190bb01b20bc5b7c2d0 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fcd867f36081908c88c55a6a1404c1 completed May 7, 2026, 6:22 p.m.
PD Predicate disambiguation batch_69fcd1f47b188190b4cf4b4c748d9d03 completed May 7, 2026, 5:55 p.m.
Created at: April 28, 2026, 3:58 p.m.