Triple
T8489776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAST attack |
E200937
|
entity |
| Predicate | mitigation |
P31419
|
FINISHED |
| Object | use of TLS 1.1 or later |
—
|
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: use of TLS 1.1 or later | Statement: [BEAST attack, mitigation, use of TLS 1.1 or later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mitigation Context triple: [BEAST attack, mitigation, use of TLS 1.1 or later]
-
A.
relief
Indicates a state or action in which distress, pain, or difficulty is reduced, eased, or removed for an entity.
-
B.
remedy
Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
-
C.
moderation
Indicates that an entity exercises restraint, balance, or avoidance of extremes in its actions, behavior, or use of resources.
-
D.
controlMeasure
chosen
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.
-
E.
inhibits
Indicates that one entity prevents, restrains, or reduces the activity, effect, or occurrence of 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5596f1c8190aead21a245f21c07 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.