Triple

T4976370
Position Surface form Disambiguated ID Type / Status
Subject German federal ministries E111773 entity
Predicate policyAreaScope P60745 FINISHED
Object nationwide 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: nationwide | Statement: [German federal ministries, policyAreaScope, nationwide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: policyAreaScope
Context triple: [German federal ministries, policyAreaScope, nationwide]
  • A. commonPolicyArea
    Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
  • B. coversPolicyArea
    Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
  • C. isPartOfPolicyArea
    Indicates that one policy, topic, or issue belongs to, falls under, or is categorized within a broader policy area or domain.
  • D. influencedPolicyArea
    Indicates that one entity has affected, shaped, or guided the development, direction, or implementation of a particular policy area associated with another entity.
  • E. policyFocus
    Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
  • 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_69bd441a0eb481908050fa4273b19eae completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd730a7590819088ab8d49c5c88c2f completed March 20, 2026, 4:17 p.m.
PD Predicate disambiguation batch_69bd7146e6e881908a55ab2756b631f6 completed March 20, 2026, 4:09 p.m.
PDg Predicate description generation batch_69bd73089f548190834103366e24ab40 completed March 20, 2026, 4:17 p.m.
Created at: March 20, 2026, 1:33 p.m.