Triple
T17742163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Büffel |
E442887
|
entity |
| Predicate | appliesTactic |
P75814
|
FINISHED |
| Object | scorched earth |
—
|
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 | Statement: [Operation Büffel, appliesTactic, scorched earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesTactic Context triple: [Operation Büffel, appliesTactic, scorched earth]
-
A.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
-
C.
tacticInspiredBy
Indicates that a tactic is derived from, influenced by, or modeled after another tactic or source.
-
D.
hasPrimaryTactic
chosen
Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
-
E.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ace58988190b927ca29af7a8b77 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.