Triple
T339524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Defense Strategy of the United States |
E6801
|
entity |
| Predicate | 2018Emphasis |
P3362
|
FINISHED |
| Object | great‑power competition |
—
|
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: great‑power competition | Statement: [National Defense Strategy of the United States, 2018Emphasis, great‑power competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2018Emphasis Context triple: [National Defense Strategy of the United States, 2018Emphasis, great‑power competition]
-
A.
highlights
chosen
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
B.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
year
Indicates the specific calendar year associated with an entity, event, or fact.
-
D.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
E.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.