Triple
T29015968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekoparty Security Conference 2011 |
E737307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ekoparty Security Conference edition |
C33320
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ekoparty Security Conference edition Context triple: [Ekoparty Security Conference 2011, instanceOf, Ekoparty Security Conference edition]
-
A.
Konferenz
Eine Konferenz ist eine organisierte, meist zeitlich begrenzte Veranstaltung, bei der mehrere Personen zusammenkommen, um Informationen zu einem bestimmten Thema auszutauschen, zu präsentieren und zu diskutieren.
-
B.
cryptology conference
chosen
A cryptology conference is a formal gathering of researchers, practitioners, and students to present, discuss, and collaborate on advances in cryptography, cryptanalysis, and related security fields.
-
C.
World Wide Web conference
The World Wide Web conference is an annual international academic and industry event focused on the advancement, research, and standardization of web technologies and applications.
-
D.
program of the Electronic Frontier Foundation
A program of the Electronic Frontier Foundation is an organized initiative or project designed to protect and promote digital civil liberties, such as privacy, free expression, and innovation, through advocacy, education, and legal action.
-
E.
Internet Security Research Group
The Internet Security Research Group is a nonprofit organization dedicated to improving internet security by promoting and providing accessible, open, and automated security technologies and practices.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 28, 2026, 9:45 a.m.