Triple
T8489757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAST attack |
E200937
|
entity |
| Predicate | targetsVersion |
P81855
|
FINISHED |
| Object | TLS 1.0 |
—
|
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: TLS 1.0 | Statement: [BEAST attack, targetsVersion, TLS 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsVersion Context triple: [BEAST attack, targetsVersion, TLS 1.0]
-
A.
targetRelease
Indicates the specific release or version that an item (such as a feature, fix, or component) is planned or designated to be delivered in.
-
B.
principalVersionFor
Indicates a relationship where one version of an entity is designated as the primary or authoritative version for another related entity.
-
C.
targetPlatformGeneration
chosen
Indicates the generation or version of the platform that an action, resource, or entity is specifically intended to run on or be compatible with.
-
D.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
E.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to 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.