Triple
T3954690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriotic War of 1812 |
E84948
|
entity |
| Predicate | strategyUsed |
P13064
|
FINISHED |
| Object | scorched-earth policy by Russian forces |
—
|
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: scorched-earth policy by Russian forces | Statement: [Patriotic War of 1812, strategyUsed, scorched-earth policy by Russian forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyUsed Context triple: [Patriotic War of 1812, strategyUsed, scorched-earth policy by Russian forces]
-
A.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
-
B.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
C.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
D.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
E.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.