Triple

T29015994

Position	Surface form	Disambiguated ID	Type / Status
Subject	Ekoparty Security Conference 2011	`E737307`	entity
Predicate	relatedAttack	`P201468`	FINISHED
Object	BEAST BEAST is a cryptographic attack that exploited vulnerabilities in the SSL/TLS protocol to decrypt secure HTTPS traffic in real time.	`E1846335`	NE 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: BEAST | Statement: [Ekoparty Security Conference 2011, relatedAttack, BEAST]

NEDg Description generation gpt-5.1

Instruction

Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"

Input

Entity: BEAST
Triple: [Ekoparty Security Conference 2011, relatedAttack, BEAST]

Generated description

BEAST is a cryptographic attack that exploited vulnerabilities in the SSL/TLS protocol to decrypt secure HTTPS traffic in real time.

Provenance (5 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_69f077ee19f881909af48f9cab00a2e5`	completed	April 28, 2026, 9:03 a.m.
NER	Named-entity recognition	`batch_69fffa3c9b288190ab967e45619c3a7e`	completed	May 10, 2026, 3:23 a.m.
NED1	Entity disambiguation (via context triple)	`batch_6a2505cdabdc8190818c4b7da541b5e1`	completed	June 7, 2026, 5:46 a.m.
NEDg	Description generation	`batch_6a250a0727108190bc085f034870e22e`	completed	June 7, 2026, 6:04 a.m.
NED2	Entity disambiguation (via description)	`batch_6a250f52bc788190a19327674f832883`	completed	June 7, 2026, 6:27 a.m.

Created at: April 28, 2026, 9:45 a.m.