Triple

T24894923
Position Surface form Disambiguated ID Type / Status
Subject Tunguska Nature Reserve E623111 entity
Predicate russianDesignation P158134 FINISHED
Object zapovednik 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: zapovednik | Statement: [Tunguska Nature Reserve, russianDesignation, zapovednik]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: russianDesignation
Context triple: [Tunguska Nature Reserve, russianDesignation, zapovednik]
  • A. SovietDesignation
    Indicates that an entity has been assigned an official designation or code name by Soviet authorities or according to Soviet classification systems.
  • B. commanderSideRussia
    Indicates that the commander is aligned with, fighting for, or acting on behalf of the Russian side in a conflict or military context.
  • C. hasMilitaryDesignation
    Indicates that an entity is assigned a specific military-related code, title, or classification.
  • D. isMilitaryAssetOf
    Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
  • E. systemDesignation
    Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
  • 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_69e2fac597708190a922bf39a49ec70a completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f464b4c9b0819085daa00c7c3b8b76 completed May 1, 2026, 8:30 a.m.
PD Predicate disambiguation batch_69f45cf017a88190b4985b11159c907d completed May 1, 2026, 7:57 a.m.
PDg Predicate description generation batch_69f464ae42e88190b3549fdf4e0b425e completed May 1, 2026, 8:30 a.m.
Created at: April 18, 2026, 5:26 a.m.