Triple

T208304
Position Surface form Disambiguated ID Type / Status
Subject Global War on Terrorism E4655 entity
Predicate policyShift P9880 FINISHED
Object expansion of U.S. counterterrorism powers 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: expansion of U.S. counterterrorism powers | Statement: [Global War on Terrorism, policyShift, expansion of U.S. counterterrorism powers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: policyShift
Context triple: [Global War on Terrorism, policyShift, expansion of U.S. counterterrorism powers]
  • A. policyApproach
    Indicates the strategy, method, or overall course of action adopted in creating, implementing, or managing a policy.
  • B. policyTool
    Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
  • C. policyStance
    Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
  • D. policyDomain
    Indicates the thematic or subject-matter area to which a given policy, rule, or regulatory action belongs.
  • 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_69a25737567c81908f9c505300239181 completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25e8b9b908190b69a3f0594b95f7e completed Feb. 28, 2026, 3:18 a.m.
PD Predicate disambiguation batch_69a25b4e3c2881908d83e8218aa9f2d9 completed Feb. 28, 2026, 3:04 a.m.
PDg Predicate description generation batch_69a25e8ade9481908d5570f6a255ee50 completed Feb. 28, 2026, 3:18 a.m.
Created at: Feb. 28, 2026, 2:51 a.m.