Triple
T8489785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAST attack |
E200937
|
entity |
| Predicate | requiresClientCondition |
P43873
|
FINISHED |
| Object | support for TLS 1.0 CBC ciphersuites |
—
|
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: support for TLS 1.0 CBC ciphersuites | Statement: [BEAST attack, requiresClientCondition, support for TLS 1.0 CBC ciphersuites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresClientCondition Context triple: [BEAST attack, requiresClientCondition, support for TLS 1.0 CBC ciphersuites]
-
A.
requiresStatus
chosen
Indicates that one entity can only proceed, be valid, or be applied if another entity has a specified status or condition.
-
B.
requiresCapability
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
-
C.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
D.
requiresContext
Indicates that the relationship or action cannot be properly understood or evaluated without additional surrounding information, conditions, or circumstances.
-
E.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
- 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.