Triple

T436563
Position Surface form Disambiguated ID Type / Status
Subject Domestic Policy Council E10022 entity
Predicate coordinatesPolicyOn P5037 FINISHED
Object domestic policy 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: domestic policy | Statement: [Domestic Policy Council, coordinatesPolicyOn, domestic policy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinatesPolicyOn
Context triple: [Domestic Policy Council, coordinatesPolicyOn, domestic policy]
  • A. locationPolicy
    Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
  • B. coordinateLocation
    Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
  • C. coversPolicyArea chosen
    Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
  • D. governingPolicy
    Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
  • E. coordinates
    Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
  • 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_69a2e8465ef481909655c681b01e2986 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2ef0c97188190b62104cb639d4b60 completed Feb. 28, 2026, 1:35 p.m.
PD Predicate disambiguation batch_69a2eddb98e081909efcf9f0a955a908 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.