Triple
T288556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Strategy of the United States |
E5938
|
entity |
| Predicate | policyLevel |
P9281
|
FINISHED |
| Object | grand strategy |
—
|
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: grand strategy | Statement: [National Security Strategy of the United States, policyLevel, grand strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyLevel Context triple: [National Security Strategy of the United States, policyLevel, grand strategy]
-
A.
policyDomain
Indicates the thematic or subject-matter area to which a given policy, rule, or regulatory action belongs.
-
B.
policyTool
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
C.
policyApproach
Indicates the strategy, method, or overall course of action adopted in creating, implementing, or managing a policy.
-
D.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
E.
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.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2f5c0081908e548b314f5e986d |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7c1448819082064f474633acd5 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d3463648190ac716d7475378536 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.