Triple

T35871566
Position Surface form Disambiguated ID Type / Status
Subject OSCE Special Monitoring Mission to Ukraine E1037238 entity
Predicate reportsAccessibility P185363 FINISHED
Object public 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: public | Statement: [OSCE Special Monitoring Mission to Ukraine, reportsAccessibility, public]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reportsAccessibility
Context triple: [OSCE Special Monitoring Mission to Ukraine, reportsAccessibility, public]
  • A. accessibilityFeatures
    Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
  • B. valueAccessibility
    Indicates how easily or readily a value can be obtained, used, or understood by relevant parties.
  • C. accessibilityPolicy
    Indicates that an entity has, follows, or is governed by a specific accessibility policy defining how it ensures access for people with disabilities.
  • D. offersAccessibilityService
    Indicates that an entity provides services or features designed to improve accessibility for people with disabilities or specific access needs.
  • E. currentAccessibility
    Indicates the present state or level of how easily something can be accessed or used.
  • 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_69f76e1e701c8190a4990d4978ce4fe6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7be53890081909b1d93f30a8f31c6 completed May 3, 2026, 9:29 p.m.
PD Predicate disambiguation batch_69f7bccacbac8190978976324c67db28 completed May 3, 2026, 9:23 p.m.
PDg Predicate description generation batch_69f7be520f148190ba200bf3dbf40656 completed May 3, 2026, 9:29 p.m.
Created at: May 3, 2026, 4:06 p.m.