Triple
T2337706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oboe |
E44348
|
entity |
| Predicate | countermeasuresFaced |
P38303
|
FINISHED |
| Object | German jamming attempts |
—
|
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: German jamming attempts | Statement: [Oboe, countermeasuresFaced, German jamming attempts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countermeasuresFaced Context triple: [Oboe, countermeasuresFaced, German jamming attempts]
-
A.
controlMeasure
Indicates a relationship where one entity implements or applies a method, action, or mechanism to regulate, mitigate, or manage a risk, process, or condition associated with another entity.
-
B.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
C.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
D.
safeguardingMeasuresInclude
Indicates that certain specific protective or security measures are contained within, or form part of, a broader set of safeguarding measures.
-
E.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6f4245881909282b3184a288e2a |
completed | March 7, 2026, 6:34 a.m. |
Created at: March 4, 2026, 7:51 p.m.