Triple

T316367
Position Surface form Disambiguated ID Type / Status
Subject Government of the Russian Federation E7714 entity
Predicate administrativeRole P5518 FINISHED
Object oversees federal executive bodies 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: oversees federal executive bodies | Statement: [Government of the Russian Federation, administrativeRole, oversees federal executive bodies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: administrativeRole
Context triple: [Government of the Russian Federation, administrativeRole, oversees federal executive bodies]
  • A. administeredBy
    Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
  • B. typeOfRole chosen
    Indicates that one entity specifies the kind or category of role that another entity holds or performs.
  • C. definesRole
    Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
  • D. deFactoRole
    Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
  • E. identificationRole
    Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
  • 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ea6462148190825acc57f6d2adaf completed Feb. 28, 2026, 1:15 p.m.
PD Predicate disambiguation batch_69a2e943f12c8190883854aeed974260 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.