Triple

T9568745
Position Surface form Disambiguated ID Type / Status
Subject Иван Кожедуб E230856 entity
Predicate прозвище P37280 FINISHED
Object самый результативный советский ас Второй мировой войны 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: самый результативный советский ас Второй мировой войны | Statement: [Иван Кожедуб, прозвище, самый результативный советский ас Второй мировой войны]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: прозвище
Context triple: [Иван Кожедуб, прозвище, самый результативный советский ас Второй мировой войны]
  • A. nicknamedFor
    Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
  • B. hasAffectionateNicknameFor
    Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
  • C. isOfficialNicknameOf chosen
    Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
  • D. honorificNickname
    Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
  • E. childhoodNickname
    Indicates that one entity is a nickname that was used to refer to the other entity during their childhood.
  • 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_69ca847f22188190a56e4a97625bef22 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9987cb0c8190af32a1193de54890 completed April 1, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69ccd59b960c8190966a8870a2426bd5 completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:04 p.m.