Triple
T32595085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himmelbett |
E833179
|
entity |
| Predicate | counteredByTactic |
P109536
|
FINISHED |
| Object | bomber stream |
—
|
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: bomber stream | Statement: [Himmelbett, counteredByTactic, bomber stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counteredByTactic Context triple: [Himmelbett, counteredByTactic, bomber stream]
-
A.
counterplay
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
B.
counterMeasureAgainst
chosen
Indicates a relationship where one entity serves as a response or defensive action intended to prevent, mitigate, or neutralize the effects of another entity.
-
C.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
D.
tacticOf
Indicates that one entity is a tactic, method, or strategy employed or used by another entity.
-
E.
primaryAdversaryCapabilityCountered
Indicates that a primary adversary capability is neutralized, mitigated, or otherwise rendered ineffective by a specified countermeasure or action.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: May 1, 2026, 1:05 a.m.