Triple

T32241847
Position Surface form Disambiguated ID Type / Status
Subject Gusev E823634 entity
Predicate borderRegionCooperation P12818 FINISHED
Object Russian-Polish cross-border projects 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: Russian-Polish cross-border projects | Statement: [Gusev, borderRegionCooperation, Russian-Polish cross-border projects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderRegionCooperation
Context triple: [Gusev, borderRegionCooperation, Russian-Polish cross-border projects]
  • A. borderRegime
    Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
  • B. borderRegion chosen
    Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
  • C. crossBorderCooperationStructure
    Indicates a formal arrangement or framework through which entities from different countries collaborate and coordinate activities across national borders.
  • D. crossBorderCooperationTopic
    Indicates that the relationship or action involves cooperation that takes place across national or regional borders on a specific topic or issue.
  • E. sharesBilateralCooperationArea
    Indicates that two entities engage in cooperative activities or initiatives within a specific, mutually agreed bilateral domain or sector.
  • 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_69f3490cdda88190a9d61e11252a771f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fef8c3f2388190b995ec173512945a completed May 9, 2026, 9:05 a.m.
PD Predicate disambiguation batch_69fef65975608190960b78d27e806d4f completed May 9, 2026, 8:54 a.m.
Created at: May 1, 2026, 12:40 a.m.