Triple

T34108977
Position Surface form Disambiguated ID Type / Status
Subject North-Eastern Administrative Okrug of Moscow E874784 entity
Predicate hasSecurityServices P22957 FINISHED
Object Moscow city police 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: Moscow city police | Statement: [North-Eastern Administrative Okrug of Moscow, hasSecurityServices, Moscow city police]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecurityServices
Context triple: [North-Eastern Administrative Okrug of Moscow, hasSecurityServices, Moscow city police]
  • A. hasSecurityFunction
    Indicates that an entity performs, provides, or is responsible for a security-related role, protection mechanism, or safeguarding function for another entity or system.
  • B. hasSecurityPresence chosen
    Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
  • C. hasSecurityDimension
    Indicates that something possesses or is associated with a particular aspect or dimension of security.
  • D. hasSecurityNotion
    Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
  • E. hasSecurityAuthority
    Indicates that one entity possesses the right or power to enforce, manage, or make decisions about security over another entity or resource.
  • 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_69f349a80d4481908527317d43f5c579 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ffa5f31c8881908c26e2aa52df6ece completed May 9, 2026, 9:24 p.m.
PD Predicate disambiguation batch_69ffa42aee408190ad1a5f285688b338 completed May 9, 2026, 9:16 p.m.
Created at: May 1, 2026, 1:53 a.m.